> pickle isnt going to work with deferred columns unless you implement
> __getstate__ and __setstate__.  so the issue with session.merge() is
> just an extension of that issue, correct ?  i.e. without deferreds
> merge has no issue.
>
> is it not reasonable to ask that objects which are to be serialized
> and cached not have any deferred columns ? (or they are explicitly
> loaded before caching )?

Sorry, I dont understand clearly.

I do understand that pickle saves only __dict__ when no __getstate__
defined.

So, to be cached, an object should fetch all its deferred columns (if
any) and provide all of them at __getstate__. Right?

And if an instance from cache has nothing for one of its deferred
column values, then referencing these properties after merge wont load
them from DB, but just fail?

Thanks.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to