Return-Path: 
 <ojb-dev-return-5262-apmail-db-ojb-dev-archive=db.apache.org@db.apache.org>
Delivered-To: apmail-db-ojb-dev-archive@db.apache.org
Received: (qmail 42658 invoked by uid 500); 29 Jul 2003 06:58:01 -0000
Mailing-List: contact ojb-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:ojb-dev-unsubscribe@db.apache.org>
List-Subscribe: <mailto:ojb-dev-subscribe@db.apache.org>
List-Help: <mailto:ojb-dev-help@db.apache.org>
List-Post: <mailto:ojb-dev@db.apache.org>
List-Id: "OJB Developers List" <ojb-dev.db.apache.org>
Reply-To: "OJB Developers List" <ojb-dev@db.apache.org>
Delivered-To: mailing list ojb-dev@db.apache.org
Received: (qmail 42588 invoked from network); 29 Jul 2003 06:58:00 -0000
Received: from unknown (HELO srv002.hpd.co.uk) (212.158.99.130)
  by daedalus.apache.org with SMTP; 29 Jul 2003 06:58:00 -0000
Message-ID: <6FB083FB72EFD21181D30004AC4CA18A01C8F8A7@srv002>
From: Charles Anthony <charles.anthony@hpdsoftware.com>
To: 'OJB Developers List' <ojb-dev@db.apache.org>
Subject: RE: checkpoint problem
Date: Tue, 29 Jul 2003 07:57:00 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Morning All,

>-----Original Message-----
>From: Armin Waibel [mailto:armin@code-au-lait.de]
>----- Original Message -----
>>From: "Charles Anthony" <charles.anthony@hpdsoftware.com>

[..Snip..]

>> I suspect that a cast-to-get-alternate-behaviour is the right way
>>forward.
>
>+1
>
>>Which way should be the default way ? That depends on what other
>>peoples assumptions of what the correct behaviour is. Probably, the old
>>behaviour isin correct and therefore the old behaviour should be "hidden" 
>>behind a cast.
>
>+1, name of the new "hidden" method?

How about flush :

/** Calling <code>flush</code> flushes persistent object modifications
  * made within the ODMG transaction since the last checkpoint to the
underlying database
  * transaction, but does not commit the database transaction. The ODMG
transaction 
  * retains all locks it held on those objects at the time the flush was
invoked.<br/>
  * flush is very similair to <code>checkpoint</code>, save that checkpoint 
  * <b>does</b> commit the database transaction.<p/>
  * Note : this method is <b>not</b> part of the ODMG Transaction interface.
  */
public void flush(){
 ...
}

Cheers,

Charles.


This email and any attachments are strictly confidential and are intended
solely for the addressee. If you are not the intended recipient you must
not disclose, forward, copy or take any action in reliance on this message
or its attachments. If you have received this email in error please notify
the sender as soon as possible and delete it from your computer systems.
Any views or opinions presented are solely those of the author and do not
necessarily reflect those of HPD Software Limited or its affiliates.

 At present the integrity of email across the internet cannot be guaranteed
and messages sent via this medium are potentially at risk.  All liability
is excluded to the extent permitted by law for any claims arising as a re-
sult of the use of this medium to transmit information by or to 
HPD Software Limited or its affiliates.



---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org