Page 158 - note FAQ

sentence : "Note that some database systems enable auto commit by default
for each new connection, but others don't"

This is correct for some clients, but don't for JDBC. JDBC specification request that auto commit is enabled when opnenew connection
(jdbc spec 2.1 chapter 10.1.1)

assertion (same page) : for multiple database you can't achieve atomicity using JDBC alone

It isn't correct - Oracle have two phase commit and with using database link and jdbc driver You can achieve atomicity (adminitsration database + jdbc driver alone) - two phase commit work in database side

regards

Not sure all JDBC driver follow the specs

This is not really JDBC alone.

1) fine, maybe don't

2) we need nothing except jdbc driver (or any client) - client doesn't know that data from more databases - for us it is jdbc alone

regards[/quote]

yet another :
Section 5.1.7
sentence :
"When one transaction holds a lock on an item, no concurrent trasnaction can read and/or modify this item"

It isn't true.

Oracle mantra : reader stop NEVER writer, writer stop NEVER reader , that is true MVC

regards

There is a difference between "wrong" and "not telling all about it". We had to use the latter technique often in the book, or it would be 1000 pages.