it’s not an option available at the moment, though there might be ways to avoid the collection loads (artificially zeroing them out w/o history).
if you don’t need the relationship features then you might as well just use query.delete(). Jonathan Vanasco <jonat...@findmeon.com> wrote: > I'm running a migration script, and the deletes via the ORM were creating a > performance issue. (trying to load 4 relationships 9million times adds up) > > I couldn't find any docs for this (just some references on update cascades) > so i sidestepped the issue by just running the Engine's delete on the table > directly. I'm just wondering if I missed any docs. > > -- > You received this message because you are subscribed to the Google Groups > "sqlalchemy" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sqlalchemy+unsubscr...@googlegroups.com. > To post to this group, send email to sqlalchemy@googlegroups.com. > Visit this group at http://groups.google.com/group/sqlalchemy. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
