i doubt this was any faster in previous releases since the basic
metholodgy of cascade hasnt changed; when you attach object B to object
A, it cascades the save-update operation across the entire graph
represented by B. While there was one little fix a while back so that
it wouldnt do cascade if
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
well things like this, i.e. cascade not going over the same field of
objects over and over again, are big and obvious. smaller things, its
mostly the attributes package that adds the overhead in...i put that
package through a huge overhaul some versions ago to simplify it, and i
ran it
Daniel Miller wrote:
Lately I've been noticing severe slowness when instantiating new SA
objects...
Oh yeah, I forgot to mention that many of my class constructors take a parent
object as one of their arguments, which explains the slow instantiation.
cascade_test.py demonstrates that the
