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 repeatedly through profiling to try to cut it down as much as possible. the key is to remove as much on_set/on_get behavior as possible and move it all to the "lets just figure it all out at flush time" stage.
but for it to be much faster at this point would require a major paradigm shift in how it works. when you look at it, some of what it does might appear wasteful but then, theres usually a unit test that will break if you try to simplify it further. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
