Hi Charles,
Charles Anthony wrote:
Hi,
Someone asked for this recently, and I'm afraid I was too busy to reply.
No problem :-)
When you lock an object (for update), it is *before* you make any changes to
it. How can OJB know when to "automatically" flush changes to the database ?
It can't; yo
tember 2003 08:38
To: OJB Users List
Subject: Re: query before commit problem
Hi Armin,
what do you think to make it configurable. For managed enviroment
the default would be a write through (or call it auto flush).
I can not access the cvs so I can not test your new Tx implementation. :-(
best reg
nection/tx.
regards,
Armin
- Original Message -
From: "Guido Beutler" <[EMAIL PROTECTED]>
To: "OJB Users List" <[EMAIL PROTECTED]>
Sent: Monday, September 15, 2003 1:13 PM
Subject: Re: query before commit problem
Hi,
how to do it in managed enviromen
rations on connection without
commit the connection/tx.
regards,
Armin
- Original Message -
From: "Guido Beutler" <[EMAIL PROTECTED]>
To: "OJB Users List" <[EMAIL PROTECTED]>
Sent: Monday, September 15, 2003 1:13 PM
Subject: Re: query before commit p
om: "Charles Anthony" <[EMAIL PROTECTED]>
To: "'OJB Users List'" <[EMAIL PROTECTED]>
Sent: Friday, September 12, 2003 1:52 PM
Subject: RE: query before commit problem
Hi,
As Thomas says, this is by design. However, you can force the transaction
to
ice if any query runned inside that transaction could "see"
that object.
Sincerely,
Jair Jr
- Original Message -
From: "Charles Anthony" <[EMAIL PROTECTED]>
To: "'OJB Users List'" <[EMAIL PROTECTED]>
Sent: Friday, September 12
cast the transaction to
TransactionExt and invoke TransactionExt.flush
e.g. (TransactionExt) t).flush()
HTH,
Cheers,
Charles.
>-Original Message-
>From: Thomas Mahler [mailto:[EMAIL PROTECTED]
>Sent: 12 September 2003 17:48
>To: OJB Users List
>Subject: Re: query before
Hi Jair,
ODMG transaction write to the db only on tx.commit.
Thus q is not persistent in the database when you perform the first query!
All queries (also ODMG OQL!) are executed against the database. So it's
obvious that loaded != q after your query.
after commiting the transaction q is stored i
