Re: UPDATE Re: Problems with SQL SET statements
- From: "Hauser@xxxxxxxxxxxxxxx" <Hauser@xxxxxxxxxxxxxxx>
- Date: Thu, 31 Jan 2008 11:54:58 -0800 (PST)
Hi,
you have to use both SET SCHEMA and SET PATH.
The SCHEMA set with SET SCHEMA is only used to find tables, views and
aliases that are unqualified. With SET SCHEMA only a single Schema/
Library can be specified. If tables or views from more than a single
schema must be used and SQL naming is used, the tables/views must
either be qualified or an alias that points to a table in the other
library must be created in the first one.
If *Sys-Naming is used, the library set with current schema is used
almost like the current library, i.e. it is seached first to find the
tables, but if the tables are not found in the current library, all
other libraries in the library list are searched.
SET PATH is used to find Stored Procedures or User Defined Functions.
With SET PATH more than one schema can be specified. These schemas are
searched in the sequence they are listed. If SQL-Naming is used and
the stored procedures or UDFs are called unqualified, but are loceated
in the same schema as the tables, this schema must be specified in the
SQL path, even though it was set with SET CURRENT SCHEMA.
With *SYS-Naming the library list is searched for both tables/views
and stored procedures/UDFs.
Birgitta
.
- Follow-Ups:
- Re: UPDATE Re: Problems with SQL SET statements
- From: jacko
- Re: UPDATE Re: Problems with SQL SET statements
- References:
- Problems with SQL SET statements
- From: Jonathan Ball
- Re: Problems with SQL SET statements
- From: Jonathan Ball
- UPDATE Re: Problems with SQL SET statements
- From: Jonathan Ball
- Problems with SQL SET statements
- Prev by Date: Re: CHGPJE question.
- Next by Date: Re: UPDATE Re: Problems with SQL SET statements
- Previous by thread: UPDATE Re: Problems with SQL SET statements
- Next by thread: Re: UPDATE Re: Problems with SQL SET statements
- Index(es):
Relevant Pages
|