| Bug #12497 | Sequence "drop table t1; create table t1" fails in PS protocol | ||
|---|---|---|---|
| Submitted: | 10 Aug 2005 14:40 | Modified: | 27 Sep 2005 9:38 |
| Reporter: | Joerg Bruehe | Email Updates: | |
| Status: | No Feedback | Impact on me: | |
| Category: | MySQL Server | Severity: | S2 (Serious) |
| Version: | 5.0.11 | OS: | Linux (Linux / i686; ICC) |
| Assigned to: | Assigned Account | CPU Architecture: | Any |
[27 Aug 2005 9:38]
Andrey Hristov
Hi Joerg, I cannot reproduce it with very fresh snapshot. Could you still reproduce it?
[27 Sep 2005 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".
Description: Release build of 5.0.11, based on ChangeSet 1.1950.1.1 05/08/06 03:10:35 kent@mysql.com +1 -0 make_win_src_distribution.sh: Added missing backslashes Test suite failure: func_group [ fail ] Errors are (from PATH/mysqltest-time) : At line 382: unable to execute statement 'create table t1 (USR_ID integer not null, MAX_REQ integer not null, constraint PK_SEA_USER primary key (USR_ID)) engine=InnoDB': Table 't1' already exists (mysql_stmt_errno=1050 returned=1) occurred: production-icc-glibc23-5.0-max.log ps-protocol Sequence in test file: 379 drop table t1, t2; 380 381 --disable_warnings 382 create table t1 (USR_ID integer not null, MAX_REQ integer not null, constraint PK_SEA_USER primary key (USR_ID)) eng ine=InnoDB; 383 --enable_warnings How to repeat: Test suite failure.