Posted by --CELKO-- on 05/29/07 16:02

>> I was actually thinking more of a solution to ignore the nulls, rather than on the fly setting them to 0. <<

Update your entire database once. Add a non-null constraint to the
columns. This is a "mop the floor, and fix the leak" philosophy.

Kill the moron who screwed up the schema, so he cannot do this
again. This is preventative maintenance :)

• Next in forum: sorting table while inserting
• Prev in forum: Re: Char or varchar for a primary key?
• Thread view: Re: needed: 1 + null = 1

[Reply to this message]