Re: different empty array syntax requirements - Mailing list pgsql-general

From Scott Ribe
Subject Re: different empty array syntax requirements
Date
Msg-id 677D08FF-2689-4038-8C30-9C720875BEC6@elevated-dev.com
Whole thread Raw
In response to Re: different empty array syntax requirements  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Apr 21, 2016, at 8:37 PM, Tom Lane <tgl@sss.pgh.pa.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-createddatabase. 

> That's a bug.  Will fix it.

OK, cool.

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







pgsql-general by date:

Previous
From: Scott Ribe
Date:
Subject: Re: different empty array syntax requirements
Next
From: Geoff Winkless
Date:
Subject: Re: Proper relational database?