I'm at ApacheCon in Atlanta where I responded to a user's question that I figured it'd be good to run by the list because I was relying solely on memory.
The question had to do with transaction management. The user thought that Derby only supports transactions in embedded mode (does not support transactions with the client jdbc driver), and there was further confusion between sql transactions and xa support. Here's what I said .... 1) Derby has always supported sql transactions in both embedded and client modes, regardless of the client jdbc driver being used. 2) XA has to do with managing distributed transactions (i.e., two phase commit). Embedded has always supported that. The Derby client jdbc driver supports it. The db2 jcc driver does not support that for derby. (I was suspected confusion left over from the early days before Derby had the client driver and the only client/server option was to download the db2 driver). how close was my answer to reality? thanks! -jean
