Merlin Moncure <mmonc...@gmail.com> wrote: > This leads to some very weird behaviors, for example 'coalesce(foo, > something)' and 'case when foo is null then something else foo end' > can give different answers. Quite apart from the issue you're pursuing, this is another example of how the COALESCE predicate in PostgreSQL is not compliant with the standard, where it is *defined as* an abbreviation of the CASE predicate. I might be persuaded otherwise by a reference to the standard, but my understanding is that the CASE predicate should be conceptually similar to the "? :" predicate in C. Does anyone else feel that these aren't implemented quite right in PostgreSQL? -Kevin
-- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
