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

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

From
tgl@postgresql.org
Date:
CVSROOT:    /cvsroot
Module name:    pgsql
Changes by:    tgl@postgresql.org    01/10/04 13:52:24

Modified files:
    src/backend/parser: parse_coerce.c
    src/backend/utils/adt: format_type.c

Log message:
    Make the world safe for atttypmod=0 ... this didn't use to mean anything,
    but timestamp now wants it to mean something.


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

From
Thomas Lockhart
Date:
>         src/backend/parser: parse_coerce.c
>         src/backend/utils/adt: format_type.c
> Log message:
>         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?

                       - Thomas

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

From
Tom Lane
Date:
Thomas Lockhart <lockhart@fourpalms.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