yeah sorry I can conceive of a potential pattern that would raise this issue but im not able to create a mapping/scenario that illustrates it. see if you can get me something on this.
On Mar 19, 2007, at 6:49 AM, svilen wrote: > > >> Michael Bayer wrote: >>> So you can take the post_update out and update to rev 2424. >> > > i have a problem with this 2424, before that was ok. > As i can't separate a short case now, here the conditions: > > multi-table-inheritance, polymorphic. Nothing else too fancy. > table_Entity has primary db_id, hand-made/sequence obj_id and other > data; > While populating the database: > ... > * SA: INFO INSERT INTO "Entity" (disabled, obj_id, atype) VALUES > (?, ?, ?) > * SA: INFO [0, 1, 'Person'] > * SA: INFO INSERT INTO "Person" (name_id, db_id) VALUES (?, ?, ) > * SA: INFO [2, 1] > > and now 2423 does: > * SA: INFO COMMIT > > while 2424 does: > * SA: INFO INSERT INTO "Entity" (disabled, obj_id, db_id, atype) > VALUES (?, ?, ?, ?) > * SA: INFO [0, 1, 1, 'Person'] > * SA: INFO ROLLBACK > > > for whatever reason it decides that the same object is dirty AND new, > and attempts to reinsert it once more. > Any idea? do u want logs? > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
