Re: current schema

Hi Tob

I believe it is in the 1992 standard - see this page - http://www.frontbase.com/docs/6.3.html

In there is the following statement in the section on users -

If no default <schema name> is given, a schema with the same spelling as the user name is created and used as default (this will happen the first time the user accesses the database).

Your point about setting the schema is right - but if nothing is set, you get a schema with the same name as the user name.

Regards
Vern

On 1/25/2016 6:39 AM, rob@xxxxxxxxx wrote:

In reply to the stuff below, just what SQL standard says the default
schema for a person will be their authorization id?

<snip>

I just want to default people's initial ODBC connection and not have
to do a SET SCHEMA.

Would this break anything of y'all if I submit a DCR to get IBM to
change this to the user profile's Current library?

The effect for SQL naming must be consistent with the standards, so a
DCR to that effect could not be accepted.
</snip>

Not that SQL Server is to be a source of the SQL standards in any way,
shape or form but they say:
<snip>
Default Schema

Users can be defined with a default schema. The default schema is the
first schema that is searched when it resolves the names of objects it
references.

The default schema for a user can be defined by using the DEFAULT_SCHEMA
option of CREATE USER or ALTER USER. If no default schema is defined for a
user account, SQL Server will assume dbo is the default schema. It is
important note that if the user is authenticated by SQL Server as a member
of a group in the Windows operating system, no default schema will be
associated with the user. If the user creates an object, a new schema will
be created and named the same as the user, and the object will be
associated with that user schema.
</snip>

A google search of "default schema" site:www.iso.org turns up no hits.

Rob Berendt