On Thu, Jul 15, 2010 at 6:05 PM, Justin Bronn <[email protected]> wrote: >> > there seems to be a problem with django postgres backend, when >> > importing data from fixtures. Data are imported correctly, but the >> > sequences for primary keys are set incorrecly on models that have >> > generic.GenericRelation field. See example: > > I have similar code, and was griping in #django-dev yesterday about > the regression. I came up with an almost identical fix (using > `m2m_db_table`), so I've accepted the ticket. > >> Of related interest would be to check if this issue existed previously >> (i.e., before the recent PostgreSQL sequence changes); if the issue >> didn't exist in Django 1.2 final, then checking the diff between the >> old and new implementations may also shed some light on potential >> solutions. > > It's definitely a side-effect of r13328 -- I have production code that > works fine on 1.2.X, but crashes on trunk without the patch when > restoring fixtures. My only question is whether there was an original > reason that `db_table` was used or if it was simply a copy & paste > oversight from the previous loop. >
I think so. And now I remember actually we discussed about this on #django-dev a couple of weeks ago but I forgot to open a ticket: http://botland.oebfare.com/logger/django-dev/2010/6/23/1/#02:04-2311026 Regards, -- Ramiro Morales | http://rmorales.net -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
