Awesome! Thank you very much indeed for the follow-up. After turning of expire_on_commit, saving a newly created object takes less than 1/3 of a second even with 100K objects in memory.
It's always nice to find the "fast = True" switch. :-) On Sep 23, 6:00 pm, Michael Bayer <[EMAIL PROTECTED]> wrote: > I misread your ticket and the resolution has been corrected. The > commit() operation expires all objects present in the session as > described > inhttp://www.sqlalchemy.org/docs/05/session.html#unitofwork_using_commi... > . Turn off expire_on_commit to disable the expiration operation, > which normally would loop through all 100K objects and set an > expiration flag for all of their attributes. Keep in mind that if any > concurrent transactions take place subsequent to the end of your > transaction, with expire_on_commit=False you may be operating with > stale data. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
