Bug #23207 Documentation for MySQL Connector/J does not mention non-functionality

• Submitted: 12 Oct 2006 10:29
• Modified: 4 Dec 2006 13:57
• Reporter: Peter Toye
• Status: Closed
• Category: Connector / J
• Severity: S3 (Non-critical)
• Version: 3.1.12
• OS: Windows (Windows)
• CPU Architecture: Any

[12 Oct 2006 10:29] Peter Toye

Description:
The current supported version (3.1.12 as I understand it) of MySQL Connector/J does not support the cancel() or query timeout features. While this is in accordance with the specification of JDBC, it should be mentioned as a restriction in Seciton 1.3.2 of the reference manual.

How to repeat:
n/a

Suggested fix:
Amend the manual (until V.5 is out of beta and fully supported).

[12 Oct 2006 12:58] Mark Matthews

Version 5 isn't beta, it's GA.

[12 Oct 2006 13:08] Peter Toye

Apologies - I'd missed the announcement of the release. Thanks for letting me know - I'll download ASAP.

Peter

[22 Oct 2006 12:04] Valeriy Kravchuk

Please, try to repeat with the latest version, 5.0.4, and inform about the results.

[22 Oct 2006 12:12] Peter Toye

Sorry, should have said that it's now working fine with v. 5.0.3 (haven't tried 5.0.4 yet).

[2 Nov 2006 9:17] Tonci Grgin

Peter, please see BUG#20650.

[2 Nov 2006 15:28] Peter Toye

Tonci,

The problem I referred to was getting MySQL to cancel an ongoing statement - I think this bug refers to a lost connection - by which time it's far too late! I did raise a forum point about lost connections, though - did your comment belong there?

Peter

[4 Dec 2006 13:57] MC Brown

The manual has been updated with the notes on support and limitations of the Statement.cancel() and Statement.setQueryTimeout() functionality.