Bug #31325 | Falcon fails to create table if in specific db | ||
---|---|---|---|
Submitted: | 1 Oct 2007 18:50 | Modified: | 12 Oct 2007 21:15 |
Reporter: | Nicklas Westerlund (OCA) | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server: Falcon storage engine | Severity: | S3 (Non-critical) |
Version: | 6.0.2-alpha-debug | OS: | MacOS |
Assigned to: | CPU Architecture: | Any |
[1 Oct 2007 18:50]
Nicklas Westerlund
[1 Oct 2007 20:06]
Nicklas Westerlund
falcon-t3.txt
Attachment: falcon-t3.txt (text/plain), 28.25 KiB.
[1 Oct 2007 20:07]
Nicklas Westerlund
falcon-t1.txt
Attachment: falcon-t1.txt (text/plain), 9.03 KiB.
[1 Oct 2007 20:08]
Nicklas Westerlund
Added some trace output of the two difference create table syntaxes... This does give me a second question though.. Why does falcon write to the file and then deletes it before it returns 'error, couldn't create the table' ?
[12 Oct 2007 17:28]
Kevin Lewis
Miguel, Can this be verified?
[12 Oct 2007 21:15]
Giuseppe Maxia
Can't repeat the described behavior using MySQL 6.0.2 on Mac OS X or MySQL 6.0.3 on Linux.