Start a new topic

Running SQL commands in Commander changes Database dropdown value in 9.1.1

[This topic is migrated from our old forums. The original author name has been removed]

Hi! I just upgraded from 8.0.4 to 9.1.1 and was hit by a new annoying feature. Whenever I run a SQL command in Commander the database dropdown changes value to the database I'm quering. That was not the case in 8.0.4 and I can't find a setting to change it back to the old, and much better, behavior. I work with several databases at the same time and prefer to have one as the +default schema+ to make sure I prefix some statements with the correct schema while *absolutetly not* prefix others, a workflow that is now near impossible in 9.1.1. Is there a setting for this or can it be added in a near future? Thanks.

[This reply is migrated from our old forums.]

Re: Running SQL commands in Commander changes Database dropdown value in 9.1.1
Andreas, This is now fixed in the just released 9.1.2 version. Regards Roger
[This reply is migrated from our old forums.]

Re: Running SQL commands in Commander changes Database dropdown value in 9.1.1
Hi Andreas, I found the cause for this. It will be fixed in the next maintenance release. Best Regards, Hans
[This reply is migrated from our old forums.]

Re: Running SQL commands in Commander changes Database dropdown value in 9.1.1
Hi Andreas, Thanks for reporting this. It looks like a regression bug introduced in 9.0.4. We are looking into it. Best Regards, Hans