not using public synonyms directly leads to - ORA-06550 about ruby-plsql HOT 7 CLOSED

@tortureduck can you give a full example of steps to reproduce?

from ruby-plsql.

@tortureduck. The issue is hard to reproduce without an example.
Can you provide ruby/rspec code to reproduce the issue? Is it still an issue?

from ruby-plsql.

Hi!

This should do the job, I have atm not a full ruby dev environment setup, therefore I am not able to provide a rspec, sorry for that!

Tx!

CREATE USER SDO IDENTIFIED BY SDO;
GRANT DBA TO SDO;
CONN SDO/SDO

CREATE OR REPLACE PACKAGE abctest IS
PROCEDURE testproc;
END;
/

CREATE OR REPLACE PACKAGE BODY abctest IS
PROCEDURE testproc IS
BEGIN
NULL;
END;
END;
/

from ruby-plsql.

To be honest thats pretty rare, but it probably points to some other kind of bug.

from ruby-plsql.

@tortureduck
Please have a look at tests inside the framework, here:
https://github.com/rsim/ruby-plsql/blob/master/spec/plsql/package_spec.rb#L116
and here:
https://github.com/rsim/ruby-plsql/blob/master/spec/plsql/package_spec.rb#L154

Those are tests (passing) that validate that ruby-plsql is resolving package name from both private and public synonyms.

Could you provide similar test to the ones mentioned that show in what circumstances it's failing?

from ruby-plsql.

I'm having the same problem. My oracle schema also has a package with the same name. If I comment out this line in procedure_call.rb it works:
@call_sql << "#{schema_name}." if schema_name
@tortureduck can you give details on your workaround?

from ruby-plsql.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

from ruby-plsql.