Re: SQL Naming convention and the library list

On 11/02/2009, at 10:36 AM, Jim Essinger wrote:

Just a quick question on SQL and the library list. When using STRSQL
to run some statements, I noticed that when using the SQL naming
convention (lib.file) it does not seem to use the library list to find
the file if the library is not specified. When I go into F13 and
change the session defaults to *SYS for the naming convention
(lib/file), the files are found in the library list without specifying
the library explicitly.

Working as designed. *SQL naming makes the system follow SQL conventions. Unqualified objects (e.g., tables, views, etc.) are expected to be in the default schema (a library/collection/schema with the same name as the user).

*SYS naming makes the system follow normal OS/400 behaviour and the library list is used to resolve unqualified objects.

Does this behavior also follow for the RUNSQLSTM command?

Yes, All OS/400 SQL interfaces behave this way.

Can I make SQL to look in the library list for files while using the
SQL naming convention with STRSQL and/or RUNSQLSTM?

No.

Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists

http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------