one of the benefis of an object persistent framework like Castor JDO is that it encapsulates the different RDBMS.
But in the following case Castor JDO does not and I don't know how to work around...
Assume a simple class
class Customer {
int id;
java.lang.String name;
}This class is mapped to a simple table CUST ( id integer primary key, name varchar(32) ).
Two instances of my program are running,
In the first one the user creates a new customer, so Castor executes an insert into the CUST table.
The transaction is still pending.
In the second one the user trie sto get a list of all existing customers. This query is executing successfully with Oracle but it fails when using MS SQL Server or SAP DB (MaxDB) after the request timeout, because these databases achieve the isolation level "committed-read" by locking an inserted record exclusively and locking a selected record shared.
This difference could be encapsulated by Castor JDO by treating insert the same as update/delete where the SQL statements are deferred until the transaction is committed.
Please let me know what You think about this problem? Did anyone solve the problem or work around it? Or is there a way to tell Castor JDO to defer the insert.
BTW: The simple work-around to commit the first transaction (the inserting one) when the customer was created does not work in my application (a fat client) because there are more modifications that all together must be atomic.
Regards, michael
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
