Re: [Firebird-devel] Adding NOT NULL fields with DEFAULT

[Rustam G. <fir...@ma...>]

Adriano > When engine reads a NOT NULL field with a DEFAULT, it
Adriano > executed the DEFAULT expression and returns a value.

Sorry, this is suggested solution or 3.0 behaviour ?

> What do you think?

As for me, the subj is **just not needed**.

a) Changing field from nullable to not nullable has no correlations
with fields default value - field should have the default, bu should
have no default too.

b) I think the solution may be simple - before (when) changing field
type from nullable to not nullable (and for other check too, probably)
checking record values and if some of them has incorrect values -
just bring an exception. Certainly, there can be troubles with records
visibility, exclusive access etc...

WBR, GR