From: | Kevin Grittner <kgrittn(at)gmail(dot)com> |
---|---|
To: | dudedoe01 <marsalanaq(at)gmail(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: isnull() function in pgAdmin3 |
Date: | 2016-09-28 15:56:37 |
Message-ID: | CACjxUsNd9ev72G6PXjSuqm=rxAW_=z2sOigcwnm0M73aAEz4vw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Sep 27, 2016 at 3:12 PM, dudedoe01 <marsalanaq(at)gmail(dot)com> wrote:
> The tables I migrated from MySQL into postgreSQL have exactly the same amount
> of rows of data so the problem is inside the view being created.
Have you actually confirmed that there are any cases where
isnull(expression) yields a different result than (expression) is
null when the expression gives the same value? I'm suspicious that
an expression could be yielding a different result, perhaps based
on join conditions handling comparisons between null values
differently. Remember, for example, that in PostgreSQL NULL = NULL
does not evaluate to TRUE.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | jotpe | 2016-09-28 20:17:26 | Graphical entity relation model |
Previous Message | Thomas Kellerer | 2016-09-28 14:54:54 | Re: isnull() function in pgAdmin3 |