Nulls will cause many irregular SQL behaviour. For instance Concatenation in
a Query will produce an empty result if one of the columns is null.
It is wise to populate all columns with some default value, even if it is
Empty String for a String, or 0 for any number. Just do it in a before
insert trigger.
-----Original Message-----
From: Derricutt, Mark <[EMAIL PROTECTED]>
To: Multiple recipients of list database <[EMAIL PROTECTED]>
Date: Wednesday, 20 October 1999 12:07 PM
Subject: RE: [DUG-DB]: update sql's and null where clause entries...
>> Must 'somefield' support null values? If there is some
>> credible default
>
>I'm doing an import routine that gets manually edited/verified by the user,
>as part of the import I want to add items that were not imported but should
>be, they have a null date/value which the user is to enter. The "key" for
>this table is the objectid/date fields, but the table is essentially
unkeyed
>(its a temp. table).
>
>I think I might just set it to todays date, and flag the data as needing
>editing etc.
>
>---------------------------------------------------------------------------
> New Zealand Delphi Users group - Database List - [EMAIL PROTECTED]
> Website: http://www.delphi.org.nz
---------------------------------------------------------------------------
New Zealand Delphi Users group - Database List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
