× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi,

it's not only a question of notation.

1. *SYS naming
   - With a qualified notation Schema and File or Stored Procedure 
     must be sperated by a slash
   - With an unqualified notation the library list will be searched
     If you have tables (files) or views in different schemas (libraries)
     you either have to qualify or using *SYS naming.
   - Besides long object names (up to 30 characters) can be specified     
     in the SQL-Statement, always the System name (up to 10 characters
     will be used.
     To determine the system names, the catalog tables must be searched. 
     This additional search can degrade performance depending on the 
     number of records in the catalog tables.

2. *SQL naming
   - With a qualified notation Schema and File or Stored Procedure 
     Must be sperated by a slash
   - With an unqualified notation the tables and views are searched
     in the svhema with the name of the user unless a current schema will
     be set by using the SQL command SET CURRENT SCHEMA.
     Only 1 schema will be searched!
     If you want to use tables or views in different libraries, you
     have to use qualified notation. 
     With an unqualified notation for procedures or user defined functions
     several libraries can be searched, but you have to declare them
     by using the SQL-Command SET PATH. 
     SET PATH will not work for unqualified file access.
   - Long object names are directly used, no system name must be determined.

That are only a few considerations that comes me in mind. The list may not
be complete.

Birgitta

-----Ursprüngliche Nachricht-----
Von: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] Im Auftrag von Chris Payne
Gesendet: Donnerstag, 13. Oktober 2005 21:56
An: Midrange Systems Technical Discussion
Betreff: RE: Infocenter - find how/when *SQL naming used over *SYS

You should use *SQL naming when you want to use dots as delimiters, for
example "library.object". If you want to use slashes as delimiters than
you should use *SYS naming, so the above would be written as
"library/object". When you use *SYS naming it will use the library list
to find unqualified objects. When you use *SQL it will only look in one
default library.

Chris

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jeff Crosby
Sent: Thursday, October 13, 2005 3:44 PM
To: 'Midrange Systems Technical Discussion'
Subject: Infocenter - find how/when *SQL naming used over *SYS

Wish me luck.

I will be looking for an answer to the subject in the "new" Infocenter.

If I'm not back by Monday, send a rescue team.


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.