Bug #52401 command to edit table brings up table from wrong schema
Submitted: 26 Mar 2010 19:11 Modified: 12 Apr 2010 10:03
Reporter: [ name withheld ] Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:5.2.17 OS:Windows (7)
Assigned to: CPU Architecture:Any

[26 Mar 2010 19:11] [ name withheld ] 
Description:
I've two schemas that have a table with the same name and the same definition (but different data). "edit table" brings up data from the wrong schema.

How to repeat:
Open Workbench, open connection to server

use schema1;
select * from table1;

// this brings data from schema1.table1 correctly

use schema1;
edit table1;

// this brings up data fro schema2.table1, incorrectly

I don't know if this is reproducible, there's probably some other variable that affects this.
[29 Mar 2010 10:31] Johannes Taxacher 
verified with 5.2.16.
Problem is already fixed in repository (due to other changes in SQL editor code)
[30 Mar 2010 13:46] Tony Bedford 
An entry has been added to the 5.2.17 changelog:

In the SQL Editor, the wrong table was displayed when using EDIT. This happened if two schemata contained tables with the same name. For example, if two schemata, schema1 and schema2 both contained a table t1, then if the following SQL was entered and executed, schema2.t1 would be displayed instead of schema1.t1:

use schema1;
edit t1;
[8 Apr 2010 21:27] [ name withheld ] 
"edit table_foo" is still broken in 5.2.17. I can do "edit my_schema.table_foo", but not "use my_schema; edit table_foo".
[11 Apr 2010 15:40] Valeriy Kravchuk 
Not repeatable for me with 5.2.17 on Mac OS X. "use db; edit table1" combination works for any database.
[11 Apr 2010 15:47] Valeriy Kravchuk 
Look like that what is reported in the last comment is a duplicate of Bug #52692. Please, check.
[12 Apr 2010 4:22] [ name withheld ] 
Correct, this is a dupe of 52692... (or 52692 is a dupe of this one, because this one was filed first). But it's strange that you can reproduce 52692 and not this one.
[12 Apr 2010 10:03] Valeriy Kravchuk 
Let's say it is a duplicate of Bug #52692. 

It was my fault to NOT set this as verified. It just happened so that I understood this my fault first while checking bug #52692 on WB 5.2.17.