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.
