RE: SQL enhancements

It is interesting how some standard SQL "features" work ...

Take for example something I ran into a few days ago.

We are developing an SQL based application that access the iSeries (V5R1)
from a custom built visual basic application over ODBC.

It is apparently considered a "feature" of SQL, that if you have a library
with the same name as a user profile, anything you add to the library via
the SQL interfaces (CREATE TABLE for example) will be owned by the user
profile that just happens to have the same name as the library!

Being an old time OS/400 Systems Administrator, I found this to be quite
odd.

After talking it over with SupportLine for a week or so... I was informed
that this was working as designed when you use the *SQL naming convention.

Would any of you SQL gurus care to take a stab at explaining why any objects
added to a collection would be owned by a user account with the same name as
the collection? I still shake my head as I write this. This seems totally
disconnected from any security scheme I can think of...

Kenneth

****************************************
Kenneth E. Graap
IBM Certified Specialist
AS/400e Professional System Administrator
NW Natural (Gas Services)
keg@nwnatural.com
Phone: 503-226-4211 x5537
FAX:    603-849-0591
****************************************


-----Original Message-----
From: R. Bruce Hoffman, Jr. [mailto:rbruceh@attglobal.net]
Sent: Thursday, September 05, 2002 8:00 AM
To: midrange-l@midrange.com
Subject: Re: SQL enhancements


no copies, in addition to. The schema names on the "real" DB2 UDBs are
SYSIBM and SYSCAT. This is a move to bring the OS/400 in line with other
members of the DB2 family.

===========================================================
R. Bruce Hoffman, Jr.
 -- IBM Certified Specialist - iSeries Administrator
 -- IBM Certified Specialist - RPG IV Developer

"There is a crack in everything,
  that's how the light gets in.
    - Leonard Cohen