<p dir="ltr"><p dir="ltr">Dne 30. 11. 2016 14:53 napsal uživatel "Pavel Stehule" <<a
href="mailto:pavel.stehule@gmail.com">pavel.stehule@gmail.com</a>>:<br/> ><br /> ><br /> ><br /> >
2016-11-3013:38 GMT+01:00 Alvaro Herrera <<a
href="mailto:alvherre@2ndquadrant.com">alvherre@2ndquadrant.com</a>>:<br/> >><br /> >> Pavel Stehule
wrote:<br/> >> > 2016-11-30 2:40 GMT+01:00 Craig Ringer <<a
href="mailto:craig@2ndquadrant.com">craig@2ndquadrant.com</a>>:<br/> >> ><br /> >> > > On 30
November2016 at 05:36, Pavel Stehule <<a href="mailto:pavel.stehule@gmail.com">pavel.stehule@gmail.com</a>><br />
>>> > wrote:<br /> >> > ><br /> >> > > > The problem is in unreserved keyword
"PASSING"probably.<br /> >> > ><br /> >> > > Yeah, I think that's what I hit when trying to
changeit.<br /> >> > ><br /> >> > > Can't you just parenthesize the expression to use operators
like||<br /> >> > > etc? If so, not a big deal.<br /> >> > ><br /> >> > ???<br />
>><br/> >> "'(' a_expr ')'" is a c_expr; Craig suggests that we can just tell users<br /> >> to
manuallyadd parens around any expressions that they want to use.<br /> >> That's not necessary most of the time
sincewe've been able to use<br /> >> b_expr in most places.<br /> ><p dir="ltr">still there are one c_expr,
butwithout new reserved word there are not change to reduce it.<br /><p dir="ltr">><br /> > Now I understand<br
/>><br /> > Regards<br /> ><br /> > Pavel<br /> > <br /> >><br /> >><br /> >> --<br
/>>> Álvaro Herrera <a href="https://www.2ndQuadrant.com/">https://www.2ndQuadrant.com/</a><br />
>>PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services<br /> ><br /> >