Re: [HACKERS] Decicision needed for connect statement

Phil Thompson writes:
> I use <server>:<port> as <SQL-server> and a separate SET SCHEMA <name>
> to set the database name as (I think) this is more consistent with
> SQL/2.

I don't think I like this:

12.3 <set schema statement>

Function

Set the default schema name for unqualified <schema qualified
name>s in <preparable statement>s that are prepared in the
current SQL-session by an <execute immediate statement> or a
<prepare statement> and in <direct SQL statement>s that are invoked
directly.

...

So it means I have to do the following to really connect:

exec sql connect to server;
exec sql set scheme template1;

This only makes sense IMO if we support different schemes over one
connection. but we don't do this, do we?

Michael
--
Dr. Michael Meskes, Project-Manager | topsystem Systemhaus GmbH
meskes(at)topsystem(dot)de | Europark A2, Adenauerstr. 20
meskes(at)debian(dot)org | 52146 Wuerselen
Go SF49ers! Go Rhein Fire! | Tel: (+49) 2405/4670-44
Use Debian GNU/Linux! | Fax: (+49) 2405/4670-10