Bug #5250 | access violation when opening script file | ||
---|---|---|---|
Submitted: | 27 Aug 2004 11:59 | Modified: | 9 Sep 2004 23:16 |
Reporter: | Patrick Sheridan | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Query Browser | Severity: | S2 (Serious) |
Version: | 1.0.6 alpha | OS: | Windows (Win2000) |
Assigned to: | Michael G. Zinner | CPU Architecture: | Any |
[27 Aug 2004 11:59]
Patrick Sheridan
[6 Sep 2004 5:23]
Scott Furry
Platform: WinXP SP1 Version: 1.0.7 Beta Suggestions to repeat observations: Open Query Browser Create/open another tab for scripting (becomes Tab #2) Create/open yet another tab for scripting (becomes Tab #3) Selected the "Default" Result Set Tab (Tab #1 when Query Browser Opens) Close tab #1 with the close tab button (upper right) The display will default back to tab #2 Attempt to select tab#3 results in the access violation NOTE: Tabs retain numbering (#2,#3, etc). If you open another tab for a script file, it is given the reference "Script 3" creating two tabs with the #3 indication another access violation will occur if you select the second "Script 3" tab Suggested Fix: Array of tab references not being updated or dynamically resequenced after addition/deletion? for example: tab #1 - resultset A, tab #2 - script A, tab #3 - script B, ... delete tab #1 - array should read... tab #1 - script A, tab #2 - script B, ... add another script tab - array should read... tab #1 - script A, tab #2 - script B, tab #3 - script C,...
[9 Sep 2004 23:16]
MySQL Verification Team
I wasn't able to repeat with version 1.0.7 Beta. Please update and test again.