Re: DatastoreConnection / optimistic txs

[Craig L Russell]

Hi Erik,




Thanks,

Craig

On Apr 8, 2007, at 10:52 AM, Erik Bengtson wrote:

Maybe the best way forward here is for you to propose a change with as much detail as I would need to update the spec.

I'm afraid I don't know what you mean by "this feature" and "this
change". If you want to guarantee that the datastore connection you
get is enlisted in the JDO transaction

tx.setOptimistic(true)
tx.begin()
//do some operations here
JDOConnection conn = tx.getDataStoreConnection();
conn.getNativeConnection().execute("UPDATE TABLEB SET A=1");
conn.close();
tx.rollback();


invoked. If a flush is performed, the connection is enlisted in the
transaction.


the connection may or may not be enlisted in the transaction.


are always enlisted in the transaction :)

A flush may or may not be performed before "getDataStoreConnection" gets So, accessing the datastore connection and doing updates is not portable, since The side effect of my change proposal would make it portable since connections

we can add a flag to guarantee it.

because currently it's not ACID neither portable.

I'm in favor of breaking backward compatibility and not adding a new flag,

Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:[EMAIL PROTECTED]
P.S. A good JDO? O, Gasp!

smime.p7s
Description: S/MIME cryptographic signature