your best chance of hacking that in 0.2.8 is to use lazy=None (for noload).
as it turns out "passive_deletes" didnt really work in 0.3.2 either so Ive fixed it for 0.3.3 (as well as "noload" which also broke in version 0.3), and also added an example illustrating a full-round trip method of dealing with large collections. If your database doesnt support ON DELETE CASCADE, you can make yourself a simple MapperExtension that will delete the child objects for you (however, its not as good as the database's cascades since it can only handle one child table with no further dependencies). so if noload doesnt cut it, id advise waiting for 0.3.3 or using rev 2156 (only two revs after the release) to get the optimization youre looking for. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
