What about relationships? Object A has a too many relationship to child
object B. I read A, then read all the B children. I then serialize A.
After de-serializing A, when I read all B children are they read from
the database or are they already loaded because they where serialized
when I serialized A?
Zissis Trabaris * Chief Technology Officer * INSYSWARE * 3235 West River
Road, Grand Island, New York, 14072, USA
Mobile (716) 930-5654 * Office (518) 636-4118 * Fax (716) 625-1305 *
z.trabari..nsysware.com * www.insysware.com
CONFIDENTIALITY: This email (including any attachments) may contain
confidential, proprietary and privileged information, and unauthorized
disclosure or use is prohibited. If you received this email in error,
please notify the sender and delete this email from your system. Thank
you.
-----Original Message-----
From: Andrey Razumovsky [mailto:razumovsky.andre..mail.com]
Sent: Sunday, March 29, 2009 3:35 AM
To: use..ayenne.apache.org
Subject: Re: Serialization and de-serialization or ROP objects
Why not? ROP objects are obviously serializable, and their
"objectContext"
field is transient, so no problems should occur. You should only watch
that
all objects have correct persistenceState (e.g. they are not COMMITED
without being registered to objectContext)
2009/3/27 Zissis Trabaris <z.trabari..nsysware.com>
> The question at hand is: Given an ROP client object retrieved from the
> database, can I serialize it to disk, later on, de-serialize it to
> memory, register it to a context and use it as if it came from the
> database? Some caveats of course... Assume the database did not change
> since the serialization process took place.
>
>
>
> Zissis Trabaris * Chief Technology Officer * INSYSWARE * 3235 West
River
> Road, Grand Island, New York, 14072, USA
> Mobile (716) 930-5654 * Office (518) 636-4118 * Fax (716) 625-1305 *
> z.trabari..nsysware.com
<mailto:%20%20z.trabari..nsysware.com<20%2520z.trabaris@insysware.com>>
> *
> www.insysware.com <http://www.insysware.com/>
>
> ________________________________
>
> CONFIDENTIALITY: This email (including any attachments) may contain
> confidential, proprietary and privileged information, and unauthorized
> disclosure or use is prohibited. If you received this email in error,
> please notify the sender and delete this email from your system. Thank
> you.
>
>
>
>
This archive was generated by hypermail 2.0.0 : Sun Mar 29 2009 - 04:07:06 EDT