> So for now id turn > the autoflush off and flush changes manually when database state is > needed..while i noticed that turning off autoflush entirely seems to > prevent the proper generation of primary keys here, it makes it all > the way to the commit() and the point of issuing SQL in about 7 seconds.
Thanks for the feedback! Indeed, just turning off autoflush and doing no other modifications gives an IntegrityError. In a second version, I turned off autoflush and did a manual flush after each save. This brought the time down from 27 to 18 seconds. Then I started randomly looking for the minimal set of flushes which didn't produce the error. This brought the time down to under 8 sec. My database state should be OK if I don't get an error? I'm rather new to databases, so I don't know too much about this integrity error (whether it's a feature or a bug), or when to do the flushing... Peter --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
