From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org, pgsql-interfaces(at)postgresql(dot)org |
Subject: | Re: Schemas: status report, call for developers |
Date: | 2002-05-26 04:42:58 |
Message-ID: | 200205260442.g4Q4gwW03949@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-interfaces |
Tom Lane wrote:
> bar were in my search path, so I should not see them unless I give a
> qualified name (eg, "\d foo.mytab" or "\d bar.mytab"). For commands
> that accept wildcard patterns, what should happen --- should "\z my*"
> find these tables, if they're not in my search path? Is "\z f*.my*"
> sensible to support? I dunno yet.
I am still reading the thread, but I thought \z mytab should show only
the first match, like SELECT * from mytab, and \z *.mytab should show
all matching tables in the schema search path. This does make '.' a
special character in the psql wildcard character set, but as no one uses
'.' in a table name, I think it is OK.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Joe Conway | 2002-05-26 06:24:21 | sample SRF: SHOW ALL equiv C function returning setof composite |
Previous Message | Marc G. Fournier | 2002-05-26 03:32:40 | Re: Redhat 7.3 time manipulation bug |
From | Date | Subject | |
---|---|---|---|
Next Message | lee | 2002-05-26 15:15:45 | Re: no pg_hba.conf |
Previous Message | Ron Johnson | 2002-05-24 15:32:08 | Re: if exists / where exisyts.... |