How can i set the Oracle schemaname at runtime ?
-
Limin Zhang
- Posts: 4
- Joined: Mon 27 Aug 2012 15:14
Re: How can i set the Oracle schemaname at runtime ?
Any idea? Thanks.
-
StanislavK
- Devart Team
- Posts: 1710
- Joined: Thu 03 Dec 2009 10:48
Re: How can i set the Oracle schemaname at runtime ?
Describing procedures on the context initialization was disabled in the release of dotConnect for Oracle 7. We recommend to download the latest 7.1.58 version. If you encounter any problems with it, please contact our Sales department (please specify the license number in the letter).
As for saving the schema name for package procedures, Entity Developer does so, e.g., for the 'Update from Database' wizard. To find and describe the procedure, the wizard has to properly parse its full name (i.e., determine whether the prefix is the schema or package name).
However, we will consider changing this behaviour if saving the name of the default schema is disabled.
Anyway, the "object does not exist" error should not occur in the latest version: no procedure describing is performed at the runtime, and when executing the procedure, its source is simply included into the command text (so that the Oracle server determines whether 'com_util' is a schema or a package on its own).
Please tell us if you can reproduce the issue when using the new version of dotConnect for Oracle.
As for saving the schema name for package procedures, Entity Developer does so, e.g., for the 'Update from Database' wizard. To find and describe the procedure, the wizard has to properly parse its full name (i.e., determine whether the prefix is the schema or package name).
However, we will consider changing this behaviour if saving the name of the default schema is disabled.
Anyway, the "object does not exist" error should not occur in the latest version: no procedure describing is performed at the runtime, and when executing the procedure, its source is simply included into the command text (so that the Oracle server determines whether 'com_util' is a schema or a package on its own).
Please tell us if you can reproduce the issue when using the new version of dotConnect for Oracle.