Skip site navigation (1) Skip section navigation (2)

Re: pgsql/src/backend parser/parse_coerce.c utils/ ...

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Thomas Lockhart <lockhart(at)fourpalms(dot)org>
Cc: pgsql-committers(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pgsql/src/backend parser/parse_coerce.c utils/ ...
Date: 2001-10-04 18:06:38
Message-ID: 29485.1002218798@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
Thomas Lockhart <lockhart(at)fourpalms(dot)org> writes:
>> Make the world safe for atttypmod=0 ... this didn't use to mean anything,
>> but timestamp now wants it to mean something.

> What was the effect of this?

coerce_type_typemod thought that typmod=0 meant it shouldn't perform any
length coercion.  But typmod=0 is now a valid value for timestamp ...

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2001-10-04 18:13:29
Subject: Re: timestamp resolution?
Previous:From: Tom LaneDate: 2001-10-04 18:03:13
Subject: Unhappiness with forced precision conversion for timestamp

pgsql-committers by date

Next:From: tglDate: 2001-10-04 19:13:56
Subject: pgsql/src/backend/utils/fmgr dfmgr.c
Previous:From: Thomas LockhartDate: 2001-10-04 17:57:59
Subject: Re: pgsql/src/backend parser/parse_coerce.c utils/ ...

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group