Re: Rethinking user-defined-typmod before it's too late

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Teodor Sigaev <teodor(at)sigaev(dot)ru>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Rethinking user-defined-typmod before it's too late
Date: 2007-06-15 17:29:45
Message-ID: 6271.1181928585@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Teodor Sigaev <teodor(at)sigaev(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2007-06-15 17:32:02 Re: Rethinking user-defined-typmod before it's too late
Previous Message Greg Smith 2007-06-15 17:29:36 Re: Performance Monitoring