ArrayField created with the wrong dbtype with Django 1.7

Bug #1431789 reported by Raphaël Badin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
djorm-ext-pgarray (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Vivid contains Django 1.7 and djorm-ext-pgarray 0.8.

djorm-ext-pgarray version 0.8 is not compatible with Django 1.7 migration module. One of the symptoms is that the dbtype of an ArrayField is ignored (and the default dbtype 'int' is used).

In other words, when declaring a field like this:
djorm_pgarray.fields.ArrayField(default=None, null=True, blank=True, dbtype="text")
One ends up with this in the DB: defined as integer[] instead of text[].

(Note that the project has been renamed to djorm-pgarray in version 1.0.)

Support for Django 1.7 was added in version 1.0 (see https://github.com/niwibe/djorm-pgarray/blob/master/CHANGES.md). I can confirm that the fields are created correctly with djorm-pgarray 1.0 and Django 1.7.

Revision history for this message
Matthias Klose (doko) wrote :

1.2 is now in vivid

Changed in djorm-ext-pgarray (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.