Michael Bayer wrote: > > > On Feb 19, 2009, at 4:33 PM, oberger wrote: > >> Thank you Michael, >> >> but I am not able to bring this to work. Even with a flush and a >> commit after every Statement. >> I understand the problem with dependend UPDATES/DELETES. >> >> But how is the ordering_list suposed to work? >> When I delete on entry with: del short_trip.trip_stops[1] >> >> and then flush() and commit(). The ordering_list has to do some >> work in the corresponding database table. > > im not sure, perhaps Jason can chime in on this....
For this constraint configuration you might try making the DB constraint initially deferred. Given the ordering of statement execution in the unit of work, no other ideas are coming to mind. The ordering_list itself is totally ignorant of the ORM. It doesn't issue any flushes or deletions, though one could make an implementation that did embed that level of control over the unit of work. -j --~--~---------~--~----~------------~-------~--~----~ 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 sqlalchemy+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
