Re: information_schema.columns changes needed for OLEDB

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org, Konstantin Izmailov <kizmailov(at)gmail(dot)com>
Subject: Re: information_schema.columns changes needed for OLEDB
Date: 2009-06-08 04:12:33
Message-ID: 24773.1244434353@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> On Sunday 31 May 2009 18:41:55 Tom Lane wrote:
>> AFAICS, the SQL standard demands that precision and scale fields be
>> non-null all the time for those data types where they make sense
>> (this is encoded in the CHECK CONSTRAINTs that are declared for the
>> various information-schema tables, see particularly 21.15
>> DATA_TYPE_DESCRIPTOR base table in SQL99). DATE is clearly wrong
>> per spec, but it's not the only problem.

> The DATE change is the only thing I'd be prepared to make right now.

At this point I think the clear decision is "we're not changing anything
for 8.4". I've put the issue on the TODO list for future development
cycles.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-06-08 04:16:01 Re: Partial vacuum versus pg_class.reltuples
Previous Message Bruce Momjian 2009-06-08 03:57:20 Re: pg_migrator issue with contrib