Re: Re: [Review] Add SPI_gettypmod() to return a field's typemod from a TupleDesc - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Re: [Review] Add SPI_gettypmod() to return a field's typemod from a TupleDesc
Date
Msg-id 1373244901.12837.29.camel@vanquo.pezone.net
Whole thread Raw
In response to Re: [Review] Add SPI_gettypmod() to return a field's typemod from a TupleDesc  (Noah Misch <noah@leadboat.com>)
Responses Re: Re: [Review] Add SPI_gettypmod() to return a field's typemod from a TupleDesc
List pgsql-hackers
On Sun, 2013-07-07 at 20:15 -0400, Noah Misch wrote:
> I mildly recommend we reject this patch as such, remove the TODO item,
> remove
> the XXX comments this patch removes, and plan not to add more trivial
> SPI
> wrappers.  If consensus goes otherwise, I think we should at least
> introduce
> SPI_getcollation() at the same time.  Code that needs to transfer one
> of them
> very often needs to transfer the other.  Having API coverage for just
> one
> makes it easier for hackers to miss that. 

The question is, what would one do with those values?  It's hard to see
when you would need the typmod and the collation of a result set.  There
might be cases, but enough to provide a special API for it?





pgsql-hackers by date:

Previous
From: mohsen soodkhah mohammadi
Date:
Subject: WAL
Next
From: Peter Eisentraut
Date:
Subject: Re: [PATCH] Add session_preload_libraries configuration parameter