Message-ID: <3CCF02AA.2000209@ballydev.com>
Date: Tue, 30 Apr 2002 13:46:34 -0700
From: Bill Cunningham <billc@ballydev.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020326
MIME-Version: 1.0
To: pgsql-hackers <pgsql-hackers@postgreSQL.org>,
	pgsql-interfaces <pgsql-interfaces@postgreSQL.org>
Subject: Re: Schemas: status report, call for developers
References: <21020.1020187890@sss.pgh.pa.us> <3CCED849.5040400@ballydev.com>
	<21260.1020191025@sss.pgh.pa.us>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Tom Lane wrote:

>Bill Cunningham <billc@ballydev.com> writes:
>
>>I would think this should produce the following:
>>
>
>>test=# \d mytab
>>        Table "bar.mytab"
>> Column |  Type   | Modifiers
>>--------+---------+-----------
>> f1     | text    |
>> f1     | integer |
>>
>
>>        Table "foo.mytab"
>> Column |  Type   | Modifiers
>>--------+---------+-----------
>> f2     | text    |
>> f3     | integer |
>>
>
>Even when schemas bar and foo are not in your search path?  (And,
>perhaps, not even accessible to you?)
>
>My gut feeling is that "\d mytab" should tell you about the same
>table that "select * from mytab" would find.  Anything else is
>probably noise to you --- if you wanted to know about foo.mytab,
>you could say "\d foo.mytab".
>
>However, \d is not a wildcardable operation AFAIR.  For the commands
>that do take wildcard patterns (like \z), I'm not as sure what should
>happen.
>
>			regards, tom lane
>
So we now have a default schema name of the current user? For example:

foobar@somewhere> psql testme
testme=# select * from mytab

    Table "foobar.mytab"
 Column |  Type   | Modifiers
--------+---------+-----------
 f2     | text    |
 f3     | integer |


like that? This is exactly how DB2 operates, implict schemas for each user.

- Bill Cunningham