Re: Rethinking user-defined-typmod before it's too late - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Rethinking user-defined-typmod before it's too late
Date
Msg-id 6271.1181928585@sss.pgh.pa.us
Whole thread Raw
In response to Re: Rethinking user-defined-typmod before it's too late  (Teodor Sigaev <teodor@sigaev.ru>)
Responses Re: Rethinking user-defined-typmod before it's too late  (Teodor Sigaev <teodor@sigaev.ru>)
List pgsql-hackers
Teodor Sigaev <teodor@sigaev.ru> writes:
>> I propose changing the typmodin signature to "typmodin(cstring[]) returns
>> int4", that is, the typmods will be passed as strings not integers.

> And modify ArrayGetTypmods() to ArrayGetIntegerTypmods()

Right --- the decoding work will only have to happen in one place for
our existing uses.

Is it worth providing an ArrayGetStringTypmods in core, when it won't
be used by any existing core datatypes?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Greg Smith
Date:
Subject: Re: Performance Monitoring
Next
From: Tom Lane
Date:
Subject: Re: Rethinking user-defined-typmod before it's too late