Kevin Grittner <kgri...@ymail.com> wrote: > Tom Lane <t...@sss.pgh.pa.us> wrote: >> Kevin Grittner <kgri...@ymail.com> writes: >>> Tom Lane <t...@sss.pgh.pa.us> wrote: >>>> the precedence of <= >= and <> is neither sane nor standards compliant. >>> >>> I wonder whether it would be feasible to have an option to generate >>> warnings (or maybe just LOG level messages?) for queries where the >>> results could differ. >> >> My guess (admittedly not yet based on much) is that warnings won't be too >> necessary. If a construction is parsed differently than before, you'll >> get no-such-operator gripes. > > I have a memory of running into this in real-world production code > and that it involved booleans. I'll see whether I posted something > to the community lists about it [...]
Here's what I posted when I ran into it in real-world code, although I posted simplified test cases rather than the (probably very complex) production code: http://www.postgresql.org/message-id/200712171958.lbhjwobb037...@wwwmaster.postgresql.org -- Kevin Grittner EDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
