Mailing-List: contact cayenne-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cayenne-user@incubator.apache.org
Received-SPF: pass (asf.osuosl.org: domain of marcin@ish.com.au designates
 218.214.52.22 as permitted sender)
Mime-Version: 1.0 (Apple Message framework v750)
In-Reply-To: <446D44F0.4000002@pfrog.com>
References: <6C7EF1C5-A375-4076-A8DB-F85530717ADF@objectstyle.org>
 <446D44F0.4000002@pfrog.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <AE9B9BFF-0E1D-45C0-B098-5DDA16DB7B4F@ish.com.au>
Content-Transfer-Encoding: 7bit
From: Marcin Skladaniec <marcin@ish.com.au>
Subject: Re: Caching problem?
Date: Fri, 19 May 2006 17:31:27 +1000
To: cayenne-user@incubator.apache.org

You are not mentioning if you use caching or not. For me it looks  
like you get your Child records from cache.

Marcin

On 19/05/2006, at 2:09 PM, Jeff de Vries wrote:

> Simplified version:  I have a parent table and a child table, where  
> the child table has a parent_id column and a status column.  I  
> change the status in one of the child records and commit the  
> change.  Later, I ask for the child records for the given parent  
> record, but the child record that I get back on which I changed the  
> status still has the *old* status instead of the new status.  If I  
> look at the database, the child record does have the new status  
> (and in fact I can see the update and commit as soon as I commit  
> the child record change).
>
> Why is the parent still seeing the old child status?  An additional  
> note is that I'm not using parent.getChildArray() but rather a  
> SelectQuery(Child) that matches toParent to the parent I'm  
> interested in.
>
> (This is in Cayenne 1.2B2 using PostgreSQL 8.1)
>
> Thanks,
> Jeff
>

-------------------------->
ish
http://www.ish.com.au
Level 1, 30 Wilson Street Newtown 2042 Australia
phone +61 2 9550 5001   fax +61 2 9550 4001