Thanks for the article links. Those contain great info. Most of
the material I had read before. One thing I did not know is that
the owner of a schema will be the user profile if that schema name
matches an existing user profile.
To my original question, it seems there is no way to use a library
list on a stored procedure call with SQL naming.
Alan Seiden on Wednesday, February 13, 2013 1:54 AM wrote:
In some cases, the naming mode used to create the stored procedure
may supersede the manner in which the procedure is called.
This topic is more complex than it seems. For details, I recommend
Birgitta Hauser's thorough, authoritative articles about SQL and
On 11 Feb 2013 05:55, Allen, Todd wrote:
The SPROC is called from a Java web app. The call is currently
qualified as library.sproc. Leaving out the library defaults to
the user profile name as the library. That is the expected
behavior. However, I remember reading about a way around this by
using an alias but cannot recall the details.
Allen, Todd on February 8, 2013 4:09 PM wrote:
Is there any way to use SQL naming in an unqualified (no
library) call to a stored procedure and have the library list
used? I seem to recall that an alias can be used to mimic the
library list behavior when using SQL naming.
I know system naming would be much easier but that is not an
option at this time.
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.