Bug #29269 Incomplete documentation: limitations of prepared statements.
Submitted: 21 Jun 2007 14:07 Modified: 22 Jun 2007 19:43
Reporter: Konstantin Osipov (OCA) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version: OS:Any
Assigned to: Jon Stephens CPU Architecture:Any

[21 Jun 2007 14:07] Konstantin Osipov 
Description:
The documentation on prepared statements is incomplete.
It only mentions limitations of prepared statements in the chapter "SQL Syntax for prepared statements", buried within the contents of the chapter.

A user doesn't have to use SQL syntax or read this chapter to encounter with the limitations.

The contents of the chapter is also incomplete.
It says:

It should mention these commands:

ALTER_DB, ASSIGN_TO_KEYCACHE, BACKUP_TABLE, CHANGE_DB
CHANGE_MASTER, CHECK, CHECKSUM, COMMIT, CREATE_DB, CREATE_FUNCTION, 
DROP_DB, DROP_FUNCTION, DROP_USER
FLUSH, GRANT, HA_CLOSE, HA_OPEN, HA_READ, HELP, KILL, LOAD
LOAD_MASTER_DATA, LOAD_MASTER_TABLE, PRELOAD_KEYS, PURGE,
PURGE_BEFORE, RESET, REVOKE, REVOKE_ALL
ROLLBACK, ROLLBACK_TO_SAVEPOINT, SAVEPOINT, SET_OPTION
SHOW_BINLOG_EVENTS, SHOW_BINLOGS, SHOW_CREATE, SHOW_ERRORS
SHOW_INNODB_STATUS, SHOW_MASTER_STAT, SHOW_NEW_MASTER, SHOW_SLAVE_HOSTS
SHOW_SLAVE_STAT, SHOW_WARNS, SLAVE_START, SLAVE_STOP, RESTORE_TABLE.

See also all the statements from Bug#29268.

How to repeat:
See the manual.

Suggested fix:
Introduce a separate chapter for limitations of prepared statements.
Document there this limitation and also bug#17898.
[21 Jun 2007 14:22] MySQL Verification Team 
Thank you for the bug report.
[22 Jun 2007 19:43] Jon Stephens 
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products.

See my comments to Bug #29268.
[23 Jun 2007 15:45] Jon Stephens 
We'll come with a better way of handling this issue as WL#3938.