| Bug #4304 | TRUNCATE <table of type BDB> , wrong result | ||
|---|---|---|---|
| Submitted: | 27 Jun 2004 17:25 | Modified: | 29 Jun 2004 13:29 |
| Reporter: | Matthias Leich | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server | Severity: | S2 (Serious) |
| Version: | 4.1 | OS: | Linux (Linux) |
| Assigned to: | Ramil Kalimullin | CPU Architecture: | Any |
[27 Jun 2004 17:27]
Matthias Leich
test case
Attachment: ml_err11.test (application/octet-stream, text), 269 bytes.
[27 Jun 2004 21:54]
MySQL Verification Team
Verified on Suse 9.0
[29 Jun 2004 13:29]
Ramil Kalimullin
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.
If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information
about accessing the source trees is available at
http://www.mysql.com/doc/en/Installing_source_tree.html

Description: TRUNCATE does not work on tables of the type BDB. Here is the output of my test case: drop table if exists t1 ; create table t1 ( a int, b varchar(30), primary key(a)) engine = 'BDB' ; insert into t1 values (1,'one'); commit ; truncate t1 ; affected rows: 0 select * from t1; a b 1 one My environment: Intel PC with Linux(SuSE 9.0), MySQL 4.1 source distrib. last ChangeSet@1.2014, 2004-06-27 How to repeat: Please use my test file, copy it to mysql-test/t ./mysql-test-run ml_err11