On Thu, Jul 15, 2010 at 6:05 PM, Justin Bronn 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
> > 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 #d
Okay, so after a little bit more investigation on that topic, I've found out:
1] It's changed since changeset 13328
(http://code.djangoproject.com/changeset/13328)
2] Previous versions DID reset the sequence thru GenericRelation
fields, but it did it on the right table so it worked. It just calle
Okay,
ticket created as #13941
I'll try to find out more and let you know in this thread.
Thanks,
A.
--
Ales Zoulek
+420 604 332 515
Jabber: ales.zou...@gmail.com
--
On Thu, Jul 15, 2010 a
On Thu, Jul 15, 2010 at 6:09 PM, Ales Zoulek wrote:
> Hi guys,
>
> 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
Hi guys,
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:
As a demo, those are just two models with generi
