Horton

Re: Add protransform for numeric, varbit, and temporal types

Robert Haas <robertmhaas@gmail.com>

View thread
From: Robert Haas <robertmhaas@gmail.com>
To: Noah Misch <noah@leadboat.com>
Cc: pgsql-hackers@postgresql.org
Date: 2012-02-08T14:37:01Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Add notion of a "transform function" that can simplify function calls.

On Tue, Feb 7, 2012 at 12:43 PM, Robert Haas <robertmhaas@gmail.com> wrote:
> I've committed the numeric and varbit patches and will look at the
> temporal one next.

Committed, after changing the OIDs so they don't conflict.

Here's one more case for you to ponder:

rhaas=# create table noah (i interval day);
CREATE TABLE
rhaas=# alter table noah alter column i set data type interval second(3);
DEBUG:  rewriting table "noah"
ALTER TABLE

Do we really need a rewrite in that case?  The code acts like the
interval range and precision are separate beasts, but is that really
true?

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company