Re: different empty array syntax requirements

From: Scott Ribe <scott_ribe(at)elevated-dev(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Postgresql General <pgsql-general(at)postgresql(dot)org>
Subject: Re: different empty array syntax requirements
Date: 2016-04-22 11:21:04
Message-ID: 677D08FF-2689-4038-8C30-9C720875BEC6@elevated-dev.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Apr 21, 2016, at 8:37 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> The parens turn into an actual parsetree node when
> operator_precedence_warning is on, and the cast-of-an-array hack doesn't
> know it should look through such a node.

I figured that. The mystery is why on my pg, and not on the other. I've asked the other guy to try it in a newly-created database.

> That's a bug. Will fix it.

OK, cool.

--
Scott Ribe
scott_ribe(at)elevated-dev(dot)com
http://www.elevated-dev.com/
https://www.linkedin.com/in/scottribe/
(303) 722-0567 voice

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Geoff Winkless 2016-04-22 12:21:36 Re: Proper relational database?
Previous Message Scott Ribe 2016-04-22 11:13:13 Re: different empty array syntax requirements