[Bug 1431789] [NEW] ArrayField created with the wrong dbtype with Django 1.7

[Raphaël Badin]

Public bug reported:

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.

** Affects: djorm-ext-pgarray (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to djorm-ext-pgarray in Ubuntu.
https://bugs.launchpad.net/bugs/1431789

Title:
  ArrayField created with the wrong dbtype with Django 1.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/djorm-ext-pgarray/+bug/1431789/+subscriptions