Bug #8342 | Query browser cannot execute it's own generated SQL | ||
---|---|---|---|
Submitted: | 6 Feb 2005 11:47 | Modified: | 6 Feb 2005 13:54 |
Reporter: | Matt Mower | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Query Browser | Severity: | S2 (Serious) |
Version: | 1.1.5 | OS: | Windows (WinXP) |
Assigned to: | CPU Architecture: | Any |
[6 Feb 2005 11:47]
Matt Mower
[6 Feb 2005 12:03]
Matt Mower
Looks like my bug is a duplicate of #7609. Same symptoms. I've also noticed how sometimes, if I remove the 'DROP TABLE' part of the generated SQL (and drop the table manually) then I can run the 'CREATE TABLE' part although I do still see an error in the status bar: Access violation at address 00568F76 in module 'MySQLQueryBrowser.exe'. Read of address 0000002C
[6 Feb 2005 13:54]
MySQL Verification Team
Duplicate for #7609