DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID;
	b=kY+VzNdAbU1vEZb2KGsR6DeF1r9Hsh2ho4q/im7v++QIJ6H3VoehVgBB75U+Ib5ZQ2bpQshjH/cGcNvZayh43Rs7c7c5cH5ZrEnXz3SJvGmdyYlZ2ZtYblLghRAFgUNJzuCSCZ0NRjHSgUoEYcAPvVL02dw/a3XsUnHYQYm1i3Q=;
Date: Tue, 29 May 2007 13:35:06 -0700 (PDT)
From: Richard Broersma Jr <rabroersma@yahoo.com>
Subject: Re: problems with SELECT query results
To: Joshua <joshua@joshuaneil.com>, Richard Huxton <dev@archonet.com>
Cc: pgsql-sql@postgresql.org
In-Reply-To: <465C6705.5000505@joshuaneil.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Message-ID: <267552.53183.qm@web31812.mail.mud.yahoo.com>


--- Joshua <joshua@joshuaneil.com> wrote:

> Hello,
> 
> 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.

If this should be allowed to have nulls, you should add a not null constraint to your table to
prevent this sort of thing from happening.  If a field should have zero's instead of nulls, you
should also add a default value of zero for this column.

ALTER TABLE Slparts
  ALTER COLUMN onorder SET NOT NULL,
  ALTER COLUMN onorder SET DEFAULT 0;

Regards,
Richard Broersma Jr.