On further investigation I see that this is actually per-instance
lazy, so no app-level hook will solve it.
So somehow __setstate__ needs to re-initialise the attribute.
I do actually merge() the object back into the new session, and that
is where the error first occurs. My web handling
avdd wrote:
On further investigation I see that this is actually per-instance
lazy, so no app-level hook will solve it.
So somehow __setstate__ needs to re-initialise the attribute.
in addition to the compile_mappers() step, all of your mapper() calls (or
declarative classes) need to have
I
On Dec 18, 3:04 am, Michael Bayer mike...@zzzcomputing.com wrote:
in addition to the compile_mappers() step, all of your mapper() calls (or
declarative classes) need to have been imported into the application
before any unpickling occurs. The error you see below is still
symptomatic of
On Dec 18, 12:58 pm, avdd adr...@gmail.com wrote:
# testlazy.py
No, I'm wrong. Investigating further...
--
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To post to this group, send email to sqlalch...@googlegroups.com.
To unsubscribe from this
Thanks, Mike. I was calling compile_mappers before importing the
modules. Whoops!
On Dec 18, 1:10 pm, avdd adr...@gmail.com wrote:
On Dec 18, 12:58 pm, avdd adr...@gmail.com wrote:
# testlazy.py
No, I'm wrong. Investigating further...
--
You received this message because you are
