Re: current schema

Tern,

That was the documentation for FrontBase. It mentions much about
adherence to SQL standards but also admits to using extensions.

You took that from the part of SQL standards supports the CREATE USER
part. And says that you can specify a default schema on CREATE USER. And
that if you do not specify a default on that parameter it will create a
schema named the same as the user id and use that as the default schema
for the user created in the CREATE USER. No where does it state that the
standards say the default schema is always the user id and ignores any
default schema assigned to the user id.
I would argue that the
CREATE USER MYUSER DEFAULT SCHEMA QGPL
should be the same as
CRTUSRPRF MYUSER CURLIB(QGPL)
and that the default response when in SQL and one executes
VALUES CURRENT SCHEMA
one should get QGPL and not MYUSER.

Hmm, once again, CREATE USER and ALTER USER are part of the SQL standards
but DB2 falls short.
To support these two statements IBM will either have to add a new
parameter to CRTUSRPRF for default schema or change the behavior of sql to
default the current schema to the CURLIB parameter on CRTUSRPRF.

Rob Berendt