On Apr 8, 10:37 pm, Michael Bayer [EMAIL PROTECTED] wrote:
any chance an actual Mapper is getting pickled and unpickled in that
process ? the stack trace indicates a mapper in a state that it
should never be in.
It's totally possible. I'll admit to not knowing what I'm doing in any
deep
Sorry I missed this thread up until now. I wasn't paying close
attention! Lets see if I can offer some insight.
The general idea of what I'd like to do is create the object from
the Elixir model, modify some of its attributes, pickle it in the
HTTP session. In a subsequent HTTP request,
Michael Bayer wrote:
I think if Elixir doesn't support mapped entities being pickled,
or requires end-user __getstate__/__setstate__ (i think the latter
is the more reasonable requirement), it should be explicit about
this. pickling/unpickling is a basic necessity particularly for
people
On Apr 9, 11:27 am, Jonathan LaCour [EMAIL PROTECTED]
wrote:
You bet. If this is indeed the problem, then we need to file a
ticket and fix it. I was arguing against monkeypatching the Entity
class with the custom __getstate__ and __setstate__, but didn't make
that clear.
I'm glad to help
On Apr 9, 2008, at 11:40 AM, Jonathan LaCour wrote:
To be entirely honest with you, I think you'd be better off not
attempting to pickle objects into your session, which could get out
of hand relatively quickly. It sounds like you are building up
an object across multiple HTTP requests,
Jonathan LaCour wrote:
Michael Bayer wrote:
I think if Elixir doesn't support mapped entities being pickled,
or requires end-user __getstate__/__setstate__ (i think the
latter is the more reasonable requirement), it should be
explicit about this. pickling/unpickling is a basic necessity
On Apr 8, 11:05 am, Alex Ezell [EMAIL PROTECTED] wrote:
When I do this, I receive this error that seems to occur on the merge():
Class 'History' entity name 'None' has no mapper associated with it.
I've tried supplying an entity name in the merge() call, but I'm
unsure what that name
On Apr 8, 10:12 am, Michael Bayer [EMAIL PROTECTED] wrote:
On Apr 8, 11:05 am, Alex Ezell [EMAIL PROTECTED] wrote:
When I do this, I receive this error that seems to occur on the merge():
Class 'History' entity name 'None' has no mapper associated with it.
I've tried supplying an entity
On Apr 8, 2008, at 12:50 PM, Alex Ezell wrote:
The setup_all() call seemed to solve the issue with the mapper. Now,
I'm getting an error like:
'ColumnProperty' object has no attribute 'key'
when I attempt the session.merge(). The column it seems to happen with
is defined as:
id =
On Apr 8, 1:20 pm, Michael Bayer [EMAIL PROTECTED] wrote:
On Apr 8, 2008, at 12:50 PM, Alex Ezell wrote:
The setup_all() call seemed to solve the issue with the mapper. Now,
I'm getting an error like:
'ColumnProperty' object has no attribute 'key'
when I attempt the session.merge().
On Apr 8, 2008, at 3:02 PM, Alex Ezell wrote:
On Apr 8, 1:20 pm, Michael Bayer [EMAIL PROTECTED] wrote:
On Apr 8, 2008, at 12:50 PM, Alex Ezell wrote:
The setup_all() call seemed to solve the issue with the mapper. Now,
I'm getting an error like:
'ColumnProperty' object has no attribute
Good point ;)
I've pasted it here:http://dpaste.com/43794/
Thanks for taking a look.
thats really weird. mappers still aren't compiled, or at least that
property isn't. try saying compile_mappers(). i think we need to
see how you're doing all this, though. your elixir/ORM
any chance an actual Mapper is getting pickled and unpickled in that
process ? the stack trace indicates a mapper in a state that it
should never be in.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
13 matches
Mail list logo
