Date: Tue, 29 May 2007 15:33:53 -0400
From: Lew <lew@nospam.lewscanon.com>
User-Agent: Thunderbird 1.5.0.9 (X11/20070102)
MIME-Version: 1.0
Subject: Re: problems with SELECT query results
References: <465C4B0B.4070906@joshuaneil.com> <465C5671.50907@archonet.com>
	<465C6705.5000505@joshuaneil.com>
In-Reply-To: <465C6705.5000505@joshuaneil.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID: <qv6dnWBN0OS8HcHbnZ2dnUVZ_sHinZ2d@comcast.com>
Lines: 25
To: pgsql-general@postgresql.org pgsql-sql@postgresql.org

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