From: | David Gould <daveg(at)sonic(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | amutu(at)amutu(dot)com, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #13805: plpgsql execute using expression evaluate wrong |
Date: | 2015-12-08 07:24:48 |
Message-ID: | 20151207232448.58fa8420@engels |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Tue, 08 Dec 2015 01:36:39 -0500
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> The datetime input parser tends to consider most non-alphanumeric
> characters as being insignificant except as field separators. We could
> tighten that up, but I think we should tread pretty carefully for fear of
> breaking cases that used to work. A trivial example:
...
> regression=# select '1 mon$ 1 day'::interval;
> interval
> -------------
> 1 mon 1 day
> (1 row)
>
> Trying to decide which characters are legitimate noise and which
> aren't seems like a tarbaby best not to get stuck to :-(
# select '#!1!#month,?=~&(12$[day*() '::interval;
interval
---------------
1 mon 12 days
(1 row)
I feel so ... dirty....
-dg
--
David Gould 510 282 0869 daveg(at)sonic(dot)net
If simplicity worked, the world would be overrun with insects.
From | Date | Subject | |
---|---|---|---|
Next Message | Terje Elde | 2015-12-08 07:57:45 | Re: BUG #13805: plpgsql execute using expression evaluate wrong |
Previous Message | Tom Lane | 2015-12-08 06:36:39 | Re: BUG #13805: plpgsql execute using expression evaluate wrong |