Bug #24501 Incomplete documentation around DDL with and without implicit COMMIT
Submitted: 22 Nov 2006 12:32 Modified: 19 Dec 2006 19:04
Reporter: Matthias Leich Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version: OS:
Assigned to: Paul DuBois CPU Architecture:Any

[22 Nov 2006 12:32] Matthias Leich
1. Per manual
DROP TEMPORARY TABLE does not end an ongoing transaction.
Tests show that this is also valid for
but this is nowhere mentioned in
I think this missing description is a documentation bug.

2. If it would be documented within
that CREATE/DROP TEMPORARY TABLE will not end an ongoing 
transaction it should be probably also explicit mentioned that
this (not end transaction) is NOT valid for other DDL
statements like CREATE INDEX ON <temporary table>...

3. Furthermore mentioning all DDL statements which are
accompagnied by an implicit COMMIT within
is nice but I think the implicit COMMIT should be also
mentioned within the chapters dedicated to the statements
I fear that a customer reading some DDL chapter is probably
not aware that he must also check
if his DDL does cause an implicit COMMIT.

I assume we have the problems above in MySQL 4.0 - 5.1.

How to repeat:
Please see above.
The attached test script shows some of the TEMPORARY TABLE
properties in DDL statements.
cd mysql-test
mv ml01.test t
# Create a dummy file with expected results
echo "Dummy" r/ml01.result
./mysql-test-run.pl --skip-ndb ml01
# Inspect r/ml01.reject

Suggested fix:
Please fix 1. and 2.
I do not insist on 3. though I would like it.
[22 Nov 2006 12:34] Matthias Leich
Test script

Attachment: ml01.test (application/octet-stream, text), 2.03 KiB.

[19 Dec 2006 19:04] Paul DuBois
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.

Note: Updated per points 1 and 2.