Prefix own Objects with schema/owner

[alerce]

Is there a way to prefix objects with the owner in PL/SQL Developer editor for the current logged user, when you edit it?
It does it when the object is in other schemas, but I would like to configure it for the current schema too.

 

[Marco Kalter]

No, there is currently no option for this.

 

[alerce]

It would be very usefull.
For our development cicle it would automate a manual error prone regular task.
Thanks for the answer anyway.

 

[Claus Pedersen]

There is a hidden feature for this. If you enter a space after the username when logging in ('scott '/'tiger', note the space after scott), all objects will be prefixed with the current schema name.

It may be a bug, but in your case it may come in handy.

 

[alerce]

I guess it is a bug, because of the message "The object is owned by a different user!" at compilation.
Anyway it is a good workaround for my needs. Grateful!
I keep suggesting the option for the preferences whish list anyway.
Thanks.

 

[mamv]

Thanks Claus, really nice work around. I was looking for this options for ages...

 

[Maxmix]

I vote for including explicit schema specification wherever possible, or at least to have this as option.
For example, opening the trigger living in currently connected schema:

create or replace trigger TIUA_VIPISKA_BUF
after INSERT or UPDATE  on shal.vipiska_buf
for each row
declare
begin
..........

is potentially dangerous now, because we could change connection, and then could by mistake compile trigger into another schema.

Still, sometimes it is useful to ignore object schema. For example, in the Tools|Export Tables window, I would like PSD to store owner in the export file. Then we would have choice upon importing: either "ignore" owner and import into currently connected schema (by default), or to honor the owner, saved during export, or may be even to substitute alternative owner.

 

[mamv]

Totally agree Maxmix. An option is mandatory.

 

[Karel P]

Totally agree Maxmix and mamv. An option is mandatory.

 

[herzig]

..
is potentially dangerous now, because we could change connection, and then could by mistake compile trigger into another schema.
..

I totally agree with that, but the consequence seems very wrong to me. If this should be introduced, it has to be optional of course.
If one of my colleagues would produce code including schema name, there would be trouble in the air!
Developer or Administrator is responsible to choose proper db connection including schema, in general explizit schema usage in code makes no sense to me (there are exceptions),
finally IDE is responsible to show this active connection and guard, warn, help on using such powerful (and potentially dangerous) feature like multiconnection!

At this point, I'm not completely happy with 9.01. E.g. maximized window show's part of it's content, but name of main connection is on display independant of active, maximized Window connection. (That's dangerous)

 

[Dirk.RSMG]

Hi,
we have BIG problems with this behaviour in our company.
We are using application servers each connecting to it's "own" schema on the SAME ORA-server.
So I have to be able to edit an object in schema 1 (test) and transfer it to schema 2-n (live) without changing any owner information!!!!!
In new version (9.0.2.1621) it's even NOT possible
- to load an object definition (without owner) from a sql-file
- compile it
- choose "Test" !!!!!
Test option ONLY is visible when I load object directly from database but then having schema name added to object.
I'm sorry, but from my point of view that's a "NO GO" for multi platform development

Please let the users decide how they want to work with the tool!

Regards,

Dirk

 

[herzig]

Hi Dirk,

to me everything is perfect with schema handling like it is. And I see no changes in latest PLSd. I load and compile scripts without schema definition every day. Testing /Debug only works on compiled objects, which have to be bound to a schema. I don't see any problem with that.