Michael Bayer wrote: > i doubt this was any faster in previous releases since the basic > metholodgy of cascade hasnt changed
Probably wasn't, I've just been testing with larger data sets lately. > so ive added your test with an extra assertion that the session in fact > contains 611 instances to the "test/perf" directory, and added an extra > argument to the "cascade" functions called "halt_on" which indicates to > stop cascading if a condition is met; session sets sends the condition > as "c in self" so that cascading along save/update/save-update will > cease along a branch if the instance is detected to be in the session > already (i.e. assumes all of its child instances are handled). thats > rev 2116 and the results are now: > > Create forward associations > ... > Created 610 objects in 0.62538 sec > > Create backward associations > ... > Created 610 objects in 0.52296 sec Thanks a million Mike! Works like a charm. It's interesting that it's now (slightly) faster to add them the "backward" way than it is to add them the "forward" way. I double-checked the results and I get the same behavior on my machine. Is there more room for optimization maybe? ~ Daniel --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
