From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | stuart(at)NOJUNK_ludwig(dot)ucl(dot)ac(dot)uk (Stuart Rison) |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: [GENERAL] Length of field names. |
Date: | 1998-07-13 18:54:28 |
Message-ID: | 199807131854.OAA21346@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> Yeah I guess I didn't explain that very well. Suppose you did
>
> \d test
>
> you'd get
>
> Field | Type | Length
> ------------------------------
> blah | text | var
> number | int2 | 2
> code | char() | 15
>
> [hand-made table :)]
>
> now what is was -badly- trying to say was that is you did a \d of that
> table you'd get:
>
>
> Field | Type | Length
> -----------------------------------
> Field | varchar() | 31
> Type | varchar() | 10
> Length | int2 | 2
>
> [or something like that, I'm guessing the numbers/types]
>
> so a sort of \d on a \d which would have given me the max length of field.
> If I understood Herouth's mail properly, all this information (i.e. catalog
> table) are store as 'hidden' tables in the DBMS. In Oracle it appears
> these are actually 'usable' in SQL statements -if you know their names and
> he was suggesting that the same could be of postgreSQL (I'm sorry if I got
> that all wrong Herouth).
That is \dT, no?
--
Bruce Momjian | 830 Blythe Avenue
maillist(at)candle(dot)pha(dot)pa(dot)us | Drexel Hill, Pennsylvania 19026
+ If your life is a hard drive, | (610) 353-9879(w)
+ Christ can be your backup. | (610) 853-3000(h)
From | Date | Subject | |
---|---|---|---|
Next Message | Gautam H Thaker | 1998-07-13 20:58:29 | on defining an "intersects or overlaps" operator for path and polygons |
Previous Message | Stuart Rison | 1998-07-13 18:02:07 | Re: [GENERAL] Length of field names. |