Home/ Questions/Q 8987737
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-15T21:51:48+00:00

I’m creating a schema for my DB using PostgreSQL and SQLAlchemy in declarative base

  • 0

I’m creating a schema for my DB using PostgreSQL and SQLAlchemy in declarative base and ran into a question that I think is answered but I’m somehow getting the syntax wrong.

I’m thinking of having an entry that’s a multidimensional array (I only need 2D, but I figured I’d ask for an n-dimentional array solution in case I run into other issues). I essentially need to have some_field[string][string] but am not sure of how to do that.

class SomeTable(Base):
    __tablename__ = 'some_table'
   multi_d_array = Column(postgresql.ARRAY(String)) #How do I make 2D+?

With an earlier version dimensionality was apparently unenforced (link: PostgreSQL multidimensional arrays in SQLAlchemy), but apparently this was patched (link: https://groups.google.com/forum/?fromgroups=#!topic/sqlalchemy/w4-nbMdxxUg). The documentation still says it’s unenforced (link: http://docs.sqlalchemy.org/en/latest/dialects/postgresql.html) but I just wanted to make sure the code works alright before having my DB blow up.

Thanks for helping me with my newbie question.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Postgresql itself does not enforce the dimensionality of the array – all arrays are N-dimensional even if you specify it with a specific number of dimensions. From the linked email:

    http://www.postgresql.org/docs/9.1/static/arrays.html

    “The current implementation does not enforce the declared number of dimensions either. Arrays of a particular element type are all considered to be of the same type, regardless of size or number of dimensions. So, declaring the array size or number of dimensions in CREATE TABLE is simply documentation; it does not affect run-time behavior.”

    In SQLAlchemy 0.8, the ARRAY type now includes an optional parameter “dimension=N” whereby you can give it the specific number of dimensions, which will allow the SQLAlchemy type to process incoming array data more quickly in Python (it doesn’t need to guess the number of dimensions), and also cause it to emit DDL (i.e. CREATE TABLE) with that number of dimensions specifically, but without this parameter everything would still work as is. The email you refer to is a user who wanted it to specifically say “INTEGER [][]” with that exact number of dimensions when emitting DDL, but it’s really not necessary.

    • 0