Subject | Re: [Firebird-Architect] Extended field/domain DEFAULT usage |
---|---|
Author | Dmitry Yemanov |
Post date | 2006-01-06T08:36:38Z |
"Martijn Tonies" <m.tonies@...> wrote:
However, I agree it's a quite practical solution. Perhaps we'll need a poll
to decide :-)
COLUMN NOT NULL as a DDL statement. Sorry for not being clear.
Dmitry
>default
> 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
> for each NULL value in the table.I don't like when something is misused, even if it's done in a good faith.
However, I agree it's a quite practical solution. Perhaps we'll need a poll
to decide :-)
> 2) allow adding a not null column, check for NULLs and raise an error ifThis is what I've meant, more or less. I didn't suggest to disallow ADD
> NULLs are found but no DEFAULT has been given.
COLUMN NOT NULL as a DDL statement. Sorry for not being clear.
Dmitry