I could try doing that, but it would get to be pretty hairy in one of my
other utility apps (it does more editing). This one is pretty simple,
so it made debugging easier. I'd rather just fix the problem than do
some kind of work-around. Besides, Andrus loves the fact I have an
acidic database design to break things. :-)
-----Original Message-----
From: Cris Daniluk [mailto:cris.danilu..mail.com]
Sent: Wednesday, May 25, 2005 2:48 PM
To: cayenne-deve..bjectstyle.org
Subject: Re: ObjectStore help ...
On 5/25/05, Gentry, Michael (Contractor) <michael_gentr..anniemae.com>
wrote:
> Well, I've been suspecting serialization. If I read the rows in and
do
> an immediate commitChanges() in the same Tapestry request/response
loop,
> nothing gets sent to the database (no changes). However, in the next
> request/response loop, it thinks they are modified (interestingly,
only
> the objects hanging off a relationship, not the primary object).
>
If you convert all the relationships on the object back to fault
before the end of the request, does that help? If so, it might be
something funky in the way it deserializes the relationships.
This archive was generated by hypermail 2.0.0 : Wed May 25 2005 - 15:02:48 EDT