distal-attribute
distal-attribute
distal-attribute
distal-attribute

Session Confusion

User, date Message
Written by jdurante
2 years ago
Category: General
4 posts since Wed, 03 Oct 12
Hello,

Have an interesting issue. Using 7.0.0.4156.

I have connections for our Production and Development databases, so they have the same structures. If I am connected to both, I cannot see the distinct data in each session.

For example, I open a table to view the data in the Dev DB, then I go to look at the same table on Prod DB, but I see the same data as Dev (when I know they are not the same).

If I close the Dev connection, and then look at the Prod table, I still see the Dev data. I have to completely close HeidiSQL and connect to a single session to see the correct data.

Any thoughts?

Thanks
Written by ansgar
2 years ago
4784 posts since Fri, 07 Apr 06
Probably a bug in Heidi, although I recall I also compare the session instance when detecting if the data grid should be refreshed. Will check that.
Written by ansgar
2 years ago
4784 posts since Fri, 07 Apr 06
Hm, not reproducible here. Having a localhost and a remote server with both the same database name and table name. As soon as I switch between tables, the right session is activated and the right data is loaded.
Written by jdurante
2 years ago
4 posts since Wed, 03 Oct 12
Not sure if it makes a difference, but both of my connections are remote.
Written by jdurante
2 years ago
4 posts since Wed, 03 Oct 12
Also - using SSH Tunnel.

Just tried it again, same thing.

When I go to the Dev session, the host tab changes to the correct IP, I see the /* entering session "{session}" */ in the log, and the other active session is greyed out in the tree view.

Then I switch to the Prod session and same thing, everything looks like it switched correctly.

I created a new table on Dev, and I see that table in the Prod tree view, even though it doesn't exist there. Same result after a refresh of the session.
Written by ansgar
2 years ago
4784 posts since Fri, 07 Apr 06
I guess that's a bug with SSH tunneled connections - probably their plink process is mixed up... I recall there was an issue report at Google Code.
Written by ansgar
2 years ago
4784 posts since Fri, 07 Apr 06
See issue #2832
Written by jdurante
2 years ago
4 posts since Wed, 03 Oct 12
Awesome. The port for both tunnels was 3307, so I changed one to 3308 and now it's working properly.

Thanks anse!
 

Please login to leave a reply, or register at first.