Re: [GENERAL] Same data, different results in Postgres vs. FrontBase

2006-02-19 Thread Stephan Szabo
On Sat, 18 Feb 2006, Brendan Duddridge wrote: > Hi, > > I have a query that returns 569 rows in FrontBase, but only 30 rows > in Postgres. The data is the same as I just finished copying my > entire database over from FrontBase to Postgres. > > I've reduced my problem to the following statement an

Re: [GENERAL] Same data, different results in Postgres vs. FrontBase

2006-02-18 Thread Tom Lane
Brendan Duddridge <[EMAIL PROTECTED]> writes: > I've reduced my problem to the following statement and have > discovered that FrontBase returns null rows along with the rows that > match the query and PostgreSQL only returns the not null rows. > CON.IS_SUBSCRIBED NOT IN ('X', 'P') You m

Re: [GENERAL] Same data, different results in Postgres vs. FrontBase

2006-02-18 Thread Uwe C. Schroeder
AFAIK NULL is not a value according to SQL spec, so it doesn't match in a "not in" clause (or any other value comparing clause for that matter, i.e. blabla >= 10 will not match rows where blabla is null). Therefor I'd say the result of 30 is correct. If you want to see null results too you shou

[GENERAL] Same data, different results in Postgres vs. FrontBase

2006-02-18 Thread Brendan Duddridge
Hi,I have a query that returns 569 rows in FrontBase, but only 30 rows in Postgres. The data is the same as I just finished copying my entire database over from FrontBase to Postgres.I've reduced my problem to the following statement and have discovered that FrontBase returns null rows along with t