DERBY-911Connection.setReadOnly is a no-op in Network Client. It works fine with embedded client.
DERBY-1370Embedded and client driver differ in the holdability reported inside a global transaction for statements that were created with HOLD_CURSORS_OVER_COMMIT outside the transaction
DERBY-2531client returns different connection on s.getConnection() on a statement obtained from a ConnectionPoolDataSource or XADataSource than the original connection.
DERBY-2532Client does not return SQLException on XAConnection.getXAResource() on a closed connection, Embedded does
DERBY-2547possible NullPointerException in client/am/ProductLevel
DERBY-2548NullPointerException through client/am/EncryptionManager
DERBY-2533Analysis needed on local/global interleaf of global/local connections to see if locks remaining open is acceptable, and why it gives Protocol errors with DerbyNetClient on subsequent connections to db