From: | Lew <lew(at)nospam(dot)lewscanon(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org pgsql-sql(at)postgresql(dot)org |
Subject: | Re: problems with SELECT query results |
Date: | 2007-05-29 19:33:53 |
Message-ID: | qv6dnWBN0OS8HcHbnZ2dnUVZ_sHinZ2d@comcast.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-sql |
Joshua wrote:
> Thank you all for your assistance. I did end up finding NULL in the
> 'onorder' column which should have been zero's.... this was in a test
> table that happened to have some NULL in it for one reason or another
> but I should not find this in the production version of the table.
>
> I also appreciate you pointing out the COALESCE function. I will find
> that helpful in future work.
>
> I look forward to hopefully assisting you guys with some of your
> PostgreSQL dilemmas in the future!
Please do not top-post, and be sure to acknowledge both groups to whom you
multi-posted, pgsql.sql and pgsql.general, for their help. (I don't know if
there were others.)
A more effective way to post to multiple groups is to cross-post, send to all
groups in the single message as I did here, which unifies the threads so that
all answers appear to each reader.
Multi-posting (sending to each group separately) is frustrating because it
fragments the conversation.
--
Lew
From | Date | Subject | |
---|---|---|---|
Next Message | Oliver Elphick | 2007-05-29 19:50:35 | Re: Geographic data sources, queries and questions |
Previous Message | Michael Glaesemann | 2007-05-29 18:49:49 | Re: Geographic data sources, queries and questions |
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Broersma Jr | 2007-05-29 20:35:06 | Re: problems with SELECT query results |
Previous Message | Joshua | 2007-05-29 17:46:45 | Re: problems with SELECT query results |