Keeping CURRENT_DATE and similar constructs in original format

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Keeping CURRENT_DATE and similar constructs in original format
Date: 2016-05-12 23:59:30
Message-ID: CAKFQuwbO4xPbQyvucmyjOdfj-f4s3mo+OGfjm8FN7jAfeg60wA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thursday, May 12, 2016, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us
<javascript:_e(%7B%7D,'cvml','tgl(at)sss(dot)pgh(dot)pa(dot)us');>> wrote:

>
> So what I've wanted to do for some time is invent a new expression node
> type that represents any one of these functions and can be reverse-listed
> in the same format that the input had. The attached proposed patch does
> that. (I'm not particularly in love with the node type name
> ValueFunction; anybody got a better idea?)
>
>
SQL99DateTimeFunction (or roughly whenever they were introduced)?

I agree with the premise. I took notice of it recently in explain output
on these lists using current_date. That example read like
('now'::cstring)::date which was really odd since I was at least expecting
text as the intermediate cast...

David J.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2016-05-13 00:09:24 Re: Keeping CURRENT_DATE and similar constructs in original format
Previous Message Tom Lane 2016-05-12 22:14:54 Keeping CURRENT_DATE and similar constructs in original format