[sqlalchemy] Re: sqlalchemy object serialization / deserialization

2007-12-21 Thread Lele Gaifax
On Thu, 20 Dec 2007 20:45:46 -0500 Rick Morrison [EMAIL PROTECTED] wrote: Re-implementing pickle with a JSON storage format is going to be a huge job, and really won't give you anything that you don't already get from pickle That's surely right: consider that Pickle is not simply a format,

[sqlalchemy] Re: sqlalchemy object serialization / deserialization

2007-12-20 Thread Rick Morrison
You're not going to be able to serialize Python class instances in JSON: json strings are simple object literals limited to basic Javascript types. Pickle does some pretty heavy lifting to serialize and reconstitute class instances. Easiest way to store JSON in the database is to limit the type

[sqlalchemy] Re: sqlalchemy object serialization / deserialization

2007-12-20 Thread Matt
On Dec 20, 5:04 pm, Rick Morrison [EMAIL PROTECTED] wrote: You're not going to be able to serialize Python class instances in JSON: json strings are simple object literals limited to basic Javascript types. Pickle does some pretty heavy lifting to serialize and reconstitute class instances.

[sqlalchemy] Re: sqlalchemy object serialization / deserialization

2007-12-20 Thread Rick Morrison
Hey Matt. Class hinting was a json-rpc 1.0 feature, subsequently dropped in 1.1. But that's a nit. The real problem, though is reconstituing those hints -- the machinery for reinstantiating those objects has to come from somewhere, and that somewhere is going to your code -- there is no magic