Bug #20875 TRUNCATE TABLE returns wrong affected rows counts
Submitted: 5 Jul 2006 23:01 Modified: 9 Sep 2006 16:34
Reporter: Calvin Sun Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:5.0, 5.1 OS:Linux (linux)
Assigned to: Assigned Account CPU Architecture:Any

[5 Jul 2006 23:01] Calvin Sun 
Description:
This is the equivalent of bug#20625. bug#20625 is for tracking InnoDB.

TRUNCATE TABLE gives different "affected rows" results. For a one million row test table i get a result of zero affected rows for MyISAM (which is
sort of OK as a DROP/CREATE will not return an affected row count either), but
for a cluster table with 1.000.000 rows TRUNCATE TABLE returns different number of affected rows.

How to repeat:
See bug#20625 for details.
[9 Aug 2006 16:34] Martin Skold 
Actually ndb uses drop/create now also for TRUNCATE TABLE
What row count do you see?
[9 Sep 2006 23:00] Bugs System 
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".