Subject | Re: [Firebird-Architect] Extended field/domain DEFAULT usage |
---|---|
Author | Fabricio Araujo |
Post date | 2006-01-21T02:55:10Z |
My 0,02 cents on this ;-)
On Fri, 6 Jan 2006 09:14:59 +0100, Martijn Tonies wrote:
>I don't agree here. There are other possibilities as well, some that are
>easier for the user.
>
>1) allow adding a not null column, but with a default. Evaluate the default
>for each NULL value in the table.
>2) allow adding a not null column, check for NULLs and raise an error if
>NULLs are found but no DEFAULT has been given.
I disagree on 2. The field must have a default, but the field must not
have
any nulls. That way, there is no inconsistency on data.