You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cayenne.apache.org by David Norwood <da...@virtuant.com> on 2007/03/30 03:46:15 UTC

Persistence latency overrun?

Hi,

 

I dealing with one of those overrun situations, where I have a process that
deletes DataObjects, then immediately returns to the same table to select
more, looping through the result set. Problem is, that some of the ones
returned in my select are still transient (I suppose), and are in the
process of deletion. What is the best practice to check the DataObject again
to guarantee that it is really still there?

 

TIA,

 

-david

RE: Persistence latency overrun?

Posted by David Norwood <da...@virtuant.com>.
Yessir.

 

  _____  

From: Michael Gentry [mailto:blacknext@gmail.com] 
Sent: Friday, March 30, 2007 8:24 AM
To: user@cayenne.apache.org; davidn@virtuant.com
Subject: Re: Persistence latency overrun?

 

Are you doing a dataContext.commitChanges() after you delete your
DataObjects?

/dev/mrg



On 3/29/07, David Norwood < davidn@virtuant.com <ma...@virtuant.com>
> wrote:

Hi,



I dealing with one of those overrun situations, where I have a process that 
deletes DataObjects, then immediately returns to the same table to select
more, looping through the result set. Problem is, that some of the ones
returned in my select are still transient (I suppose), and are in the 
process of deletion. What is the best practice to check the DataObject again
to guarantee that it is really still there?



TIA,



-david

Re: Persistence latency overrun?

Posted by Michael Gentry <bl...@gmail.com>.
Are you doing a dataContext.commitChanges() after you delete your
DataObjects?

/dev/mrg


On 3/29/07, David Norwood <da...@virtuant.com> wrote:
>
> Hi,
>
>
>
> I dealing with one of those overrun situations, where I have a process
> that
> deletes DataObjects, then immediately returns to the same table to select
> more, looping through the result set. Problem is, that some of the ones
> returned in my select are still transient (I suppose), and are in the
> process of deletion. What is the best practice to check the DataObject
> again
> to guarantee that it is really still there?
>
>
>
> TIA,
>
>
>
> -david
>
>
>
>
>
>