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 Lane | Date: 2001-10-04 18:13:29 |
| Subject: Re: timestamp resolution? |
| Previous: | From: Tom Lane | Date: 2001-10-04 18:03:13 |
| Subject: Unhappiness with forced precision conversion for timestamp |
pgsql-committers by date
| Next: | From: tgl | Date: 2001-10-04 19:13:56 |
| Subject: pgsql/src/backend/utils/fmgr dfmgr.c |
| Previous: | From: Thomas Lockhart | Date: 2001-10-04 17:57:59 |
| Subject: Re: pgsql/src/backend parser/parse_coerce.c utils/ ... |