| From: | mike(dot)griffin(at)mygenerationsoftware(dot)com |
|---|---|
| To: | "Bruno Wolff III" <bruno(at)wolff(dot)to> |
| Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, mike(dot)griffin(at)mygenerationsoftware(dot)com, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: 7.4's INFORMATION_SCHEMA.Columns View |
| Date: | 2004-06-19 01:11:23 |
| Message-ID: | 4585.4.160.153.201.1087607483.squirrel@4.160.153.201 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Ah yes, is that in pg_types, good idea, I might override that after I make
the query.
> On Fri, Jun 18, 2004 at 11:42:29 -0400,
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>
>> The SQL spec doesn't allow unconstrained lengths for these types
>> so it gives no guidance about what to display in the information_schema
>> views. Any opinions?
>
> It might make some sense to use the maximum length supported by the type
> for the precision. The documentations says that numeric is limited to
> 1000 digits.
>
> If there isn't a set scale for the type, then NULL would probably make the
> most sense.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-06-19 01:18:25 | Re: 7.4's INFORMATION_SCHEMA.Columns View |
| Previous Message | mike.griffin | 2004-06-19 01:09:49 | Re: 7.4's INFORMATION_SCHEMA.Columns View |