From: | Gavin Baumanis <gavinb(at)eclinic(dot)com(dot)au> |
---|---|
To: | pgsql-sql(at)postgresql(dot)org |
Subject: | SELECT MAX returns wrong value |
Date: | 2007-12-13 23:09:27 |
Message-ID: | 4761BBA7.7030800@eclinic.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Hi Everyone,
Sorry if I am missing something obvious but I think I have found a bug.
If I perform the following SQL
SELECT MAX(column) FROM table WHERE expression
and there is no match, Postgres returns a record count of 1.
There is no value in max, it is NULL.
Thus trying to perform some "other" tasks based on if a record was
returned or not is proving a little difficult in this instance.
We are using 8.1.9 on Debian.
Thanks for any help you might be able to offer.
--
If I can ever be of any further assistance, please contact me.
Gavin 'Beau' Baumanis
eClinic Pty Ltd
ABN 80 092 450 274
657 Nicholson Street
Carlton North
Victoria 3054
Australia
P: +61 3 9381 4567
F: +61 3 9381 4657
M: +61 438 545 586
E: beau(at)eclinic(dot)com(dot)au
Attachment | Content-Type | Size |
---|---|---|
gavinb.vcf | text/x-vcard | 505 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-12-13 23:32:38 | Re: SELECT MAX returns wrong value |
Previous Message | Steve Midgley | 2007-12-13 21:11:55 | Re: Query design assistance - getting daily totals |