Code Assistant editing package owned by different user

[MonDeveloper]

Hi Guys, first of all let me say the "PL/SQL Dev version 10" is amazing!

At our IT department we are trying to put in place a development model that separates the ownership of the data model to the ownership of the pl/sql development.
We reached a good point but we miss one important thing: Intellisense!

Let me introduce our scenraio: when a developer login into "PL/SQL Developer" with his own personal user and open a package owned by the schema owner he can modify and compile the package without any problem (we granted him all the necessary privileges) but when the developer try to write the code, the autocomplete option doesn't help him since he don't add the schema prefix before any table (and this is not good ).

My suggestion is, when the developer edit a packages (or any kind of pl/sql source) could you change the context of the auto-complete using as "base-owner" the owner of the package.
In my opinion this will be also more correct because the code inside the package will be executed under the package owner privileges; in addition you could add also a "switch" that uses the package owner as "base-owner" for the auto-complete option only if the developer has not specified the AUTHID CURRENT_USER clause, but this is not really necessary because in case of the AUTHID CURRENT_USER clause the IDE can't really know which user context should be used....

 

[Marco Kalter]

That is indeed a good suggestion within the context of a program unit owned by another user. I have added this to the list of enhancement requests.

 

[MonDeveloper]

Great to hear this from you!
In the meanwhile could you suggest any workaround?

 

[Marco Kalter]

No, I don't see any workaround at the moment.

 

[Claus Pedersen]

Try experimenting with the alter statement:

alter session set current_schema = <baseOwner>

where is the owner of the objects.

Also apply

set role <selectRole>

where is a role that has selects rights on all baseOwner's tables.

These commands could be placed in the afterconnect.sql/login.sql command file, so the commands are executed after each new login. I do not remember which of the files are executed when, but that is stated in the PLD manual.