Here is one I have been working on. It serializes the object with AMF
so it only needs one table. Note that your classes need to have a
[RemoteClass] metadata tag ( no alias needed) in order for them to be
deserialized correctly. Note that the static initialize method needs
to be called before
Interesting... More or less just stuffs everything into a database as
is. Doesn't leave any room for aggregate SQL statements against
stored properties, but then I didn't ask for that I guess. :)
-Cameron
On Wed, May 14, 2008 at 10:30 AM, jer_ela [EMAIL PROTECTED] wrote:
Here is one I have
You can skip the step of sending this to a ByteArray and
Base64Encoding it, by using the additional affinities added for AIR
applications. For example, using the following create statement:
CREATE TABLE vo (objID String UNIQUE NOT NULL, objValue Object);
You can then store the objects directly
This is good stuff. Definitely thanks for the responses...
-Cameron
On Wed, May 14, 2008 at 12:51 PM, jason_williams_mm
[EMAIL PROTECTED] wrote:
You can skip the step of sending this to a ByteArray and
Base64Encoding it, by using the additional affinities added for AIR
applications. For
4 matches
Mail list logo
