Problems with: session set current_schema

[Valdis1987]

Hi,
Here is snipet:

Code: Select all

alter SESSION SET CURRENT_SCHEMA = "UserM";

select sys_context('USERENV', 'CURRENT_SCHEMA') from dual
  union all
select sys_context('USERENV', 'CURRENT_USER') from dual;

and default user(schema) for db is userD

Now when i hit F5 i get:
UserM
UserD

BUT:
When i do like usually did before
F8 for session
and F8 for other statements....
I geT:
UserD
UserD

Problem came up this morning when i updated db Forge studio (Version: 3.5.185)

How can i resolve this problem? How can i set session once and use it?
Thanks.


Updated:
Problem is that now i can run session set + one statement per window.

[ShawnCruze]

Would like to much obliged for imparting this with us..It may favorably works for all of us...:)Check 'em
Google apps email delegation

[alexa]

Please note that this is a normal behavior in the new version 3.5 of dbForge Studio for Oracle which means that when performing the 'Execute Current Statement (F8)' command, the 'ALTER SESSION SET CURRENT_SCHEMA' statement is not executed anymore.

If you would like this statement to be included, you have to execute the whole script by pressing 'F5' or put 'ALTER SESSION...' right before the query that you want to execute, select the query along with 'ALTER SESSION...' and perform the 'Execute Current Statement (F8)' command.

[Valdis1987]

Hi,
Thanks for reply.

Can you tell me please, where can i find previous version dbforg for oracle?
Or how can i downgrade it?

Thanks.

[Valdis1987]

Or is there a way to get old session set behaviour, like it was before latest version?

[Valdis1987]

And now i also don't have intelisense because i don't have my user session set.

I have to write "USER".table_name......

[alexa]

Unfortunately, this is so. You have to write "USER".table_name...... or connect with the user that was used to create the object.