Working with different schema

[protos]

Hi.
In our organization all developers login in database with his own usernames/passwords. Then change current schema and working with objects in that schema. In toad there are useful functionality - combobox for change current schema.
PLSQL Developer not perfectly working in this case, even after change current schema manually "alter session...". For example Code assistant can't find objects if they written without schema name..

How we can work in this case, there are any workaround?
May be such functionality in plans?

 

[Marco Kalter]

In the upcoming 11.0 release you can define an initialization script for a connection. You can add the corresponding "alter session" statement and any other initialization in this script.

 

[protos]

it's working only for one schema. If I want to change current schema after connection, I forced out to reconnect to connection with different initialization script. It is not handy.

 

[Marco Kalter]

If you want to frequently switch the current schema for the same session, you could consider to create some session tools (Tools > Configure Tools) with the corresponding alter session statements. You can add these tools to the menu, to the toolbar, and assign a function key if necessary.

 

[protos]

Yes, but after changing current schema PLSQL developer not understand this and some functionality does not working. Such as describe table, or code assistant, or ctrl-click on table or package. I believe that is because PLSQL Dev thinks that he is in original schema.

 

[Hilarion]

I second the idea to have this function "natively" handled by the PL/SQL Developer. I also do sometimes have to work with different schemas when logged into different ones and having that ability easily switch current schema (and see what schema is current) would be great.

It would probably require a lot of work to make the application fully aware of what the current schema is and work in that context where appropriate, but the fact that people ask for it and that for example the TOAD application does handle that, shows that the feature is needed.

 

[AndrewV]

I'm probably missing something obvious but isn't the simple solution just to run two instances of PL/SQL Developer?

 

[protos]

We have limited connections per user.

 

[Hilarion]

I do not see how this solves anything. I have to log in using my personal username and work with some other specific schemas. How does launching more than one instance allow the Developer to properly handle switching current schema in a session?

 

[protos]

Hi.
What about whis problem?
Main problem - When current schema changed in initializations SQL Sсript (connection manager), than PLSQL developer not display compilation errors. It's makes use extremely uneasy.