db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bryan Pendleton <bpendleton.de...@gmail.com>
Subject Re: Derby 10.8.2.2, JTA on GlassFish 3.1.2.2 and very strange behavior
Date Mon, 18 Feb 2013 16:29:20 GMT
 > One more question, though: the uncommitted insert comes up
 > in the subsequent select - is this data coming from the server,
 > from the active tx, or does the jdbc driver cache the data somehow?

The results are coming from the server. The server shows you your own
uncommitted updates, but won't show them to any other transaction
until you commit or abort your transaction.

To be precise, some of these behaviors are controllable: see the
discussion of "isolation" in the docs:
http://db.apache.org/derby/docs/10.9/devguide/cdevconcepts30291.html

thanks,

bryan


Mime
View raw message