> 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
