You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cayenne.apache.org by Zissis Trabaris <z....@insysware.com> on 2009/06/04 08:55:15 UTC
Best way to turn a DataRow into an Object instance in ROP client?
I have a DataRow in an ROP client. Is there a way to turn it into an
object registered to a CayenneContext without doing another read to the
database?
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.trabaris@insysware.com <ma...@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.
Re: Best way to turn a DataRow into an Object instance in ROP client?
Posted by Andrus Adamchik <an...@objectstyle.org>.
> I have a DataRow in an ROP client.
> Is there a way to turn it into an
> object registered to a CayenneContext
> without doing another read to the
> database?
You can using DataObjectUtils. But this will incur a trip to the
server. Whether the server will query the DB or not depends on whether
the object has been cached already on the server.
Andrus
On Jun 4, 2009, at 9:55 AM, Zissis Trabaris wrote:
> I have a DataRow in an ROP client. Is there a way to turn it into an
> object registered to a CayenneContext without doing another read to
> the
> database?
>
>
>
> 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.trabaris@insysware.com <ma...@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.
>
>
>