On Tue, Sep 27, 2016 at 3:12 PM, dudedoe01 <marsalanaq@gmail.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
