I find myself in a situation where I need certain (normally lazy-loaded) properties of an ORM class to be eagerloaded for a particular query. I pass "withoptions=[eagerload('property')]" in to session.query(), and everything works fine. At least, it did until the query picked up a record that had been previously returned by another query without eagerloading. Because the record was already cached in the session, it didn't pick up on the eagerload option.
What I'd like to know is, is there a way to force the eagerloading query to apply its eagerloading behavior, even if the record is already cached in the session? Thanks, Cory Johns Systems Tower Hill Insurance Group, Inc. CONFIDENTIAL NOTICE: This email including any attachments, contains confidential information belonging to the sender. It may also be privileged or otherwise protected by work product immunity or other legal rules. This information is intended only for the use of the individual or entity named above. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or the taking of any action in reliance on the contents of this emailed information is strictly prohibited. If you have received this email in error, please immediately notify us by reply email of the error and then delete this email immediately. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---