Editor automatically uses schema for packages?

Toad for Oracle
1

After my latest daily crash, this time when I launched Toad (11.5), it is automatically using the schema when I try to compile a package.

For example, I have a package that belongs to abc (the default schema, not my login schema), and I can’t compile it because I’m using schema.table_name.column_name%type in the parameter section. It also fusses when trying to call another abc.package.function/procedure. In both cases, I get the error message, "object ABC.ABC is invalid

It appears to be a setting that turned itself on (or maybe off) but I can’t find any mention of it within the contents in TOAD or in the Toad Options or via google.

How do I make this stop?

Thanks!

2

Nevermind, it appears that someone created a package with the same name as the schema, abc.abc and that’s apparently what the editor thinks I’m referring to.

3

On Sep 28, 2015, at 5:16 PM, parrothead bounce-caliandrade@toadworld.com wrote:

RE: Editor automatically uses schema for packages?

Reply by parrothead
Nevermind, it appears that someone created a package with the same name as the schema, abc.abc and that's apparently what the editor thinks I'm referring to.

To reply, please reply-all to this email.

Stop receiving emails on this subject.

Or Unsubscribe from Toad for Oracle - General notifications altogether.

Toad for Oracle - Discussion Forum

Flag this post as spam/abuse.