Good news everyone!
ArrayField has been merged into django master. This
will not be backported to the upcoming 1.7 release, but it will now be in 1.8.
You can read the
Let us know if you find any errors!
The second area is indexing. While
db_index=True will work on an
ArrayField, it will create a btree index which is only useful for equality
in this case. The correct index type is a
gist index, but there is no way to
tell Django this is what I need. This will require a refactoring of
contrib.gis as well, and fits nicely within the work on
I think my next area to work on will be uuid fields, with larger primary key
fields coming out as a corrollary. The interest here will be in supporting
making fields other than
AutoField be "auto" fields - using
allow the database to calculate their values and return them.
For those interested, slides from my talk at DjangoConEurope are available online.