Subject Re: [Firebird-Architect] Extended field/domain DEFAULT usage
Author Thomas Steinmaurer
Hi!

>>And only practical if there is DDL support for changing a non-null field
>>to NOT NULL, otherwise it would mean, I won't be able to add a NOT NULL
>>field to an existing table at all.
>>
>>Regards,
>>Thomas
>>
>>
>>
>
> Hi !
>
> Or requiring that when inserting a not null field to a populated table
> it should have a default value, and that default value should be applied
> to the field.

Yup, but there might be a reason (from a database developer POV) not to
have a DEFAULT value, even if it is a NOT NULL field, IMHO.


Thomas