MySQL Bugs: #8778: result set streaming mode is misleading

Bug #8778	result set streaming mode is misleading
Submitted:	24 Feb 2005 15:29	Modified:	9 Aug 2005 19:05
Reporter:	Quartz 12h	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Connector / J Documentation	Severity:	S2 (Serious)
Version:	3.1	OS:
Assigned to:	Mark Matthews	CPU Architecture:	Any

Description:
The connector/j doc explains limits of the driver in
http://dev.mysql.com/doc/connector/j/en/cj-implementation-notes.html
The statement.setFetchSize(int size) is not implemented because ignored by the driver (same for cancel())

The Doc explains that the user can stream with some statement tips like result set forwardonly and readonly, while using a fetch size of Integer.MIN_VALUE.
Although it works, the docs says that the table wold be locked during a result set traversal.

Is that table locking only happening on MyIsam tables? (I use innodb tables in this case).

How to repeat:
I breakpointed my loop on resultset.next() and tried to change values in a table.
It isn't locked. Not that I mind at all (I much prefer it to locking) but the doc is either wrong or incomplete.

Suggested fix:
Please complete the doc to explicitely state when table locking would occur.

Thanks for your bug report.

Fixed in docs.