Subject | Re: [Firebird-Architect] Extended field/domain DEFAULT usage |
---|---|
Author | Nando Dessena |
Post date | 2006-01-05T11:14:24Z |
Adriano,
AdSF> There is another problem related with DEFAULT and GEN_ID.
AdSF> If you have a NOT NULLable field and alter a column to have a DEFAULT
AdSF> with GEN_ID, records stored in the previous format will evaluate the
AdSF> DEFAULT clause in each fetch and the generator will be incremented.
AdSF> This is at least strange.
yep. And the same goes with "DEFAULT CURRENT_TIMESTAMP" and the like.
Every time you have a non-constant or non-deterministic default
expression, actually. It's not strange, it's plain crazy.
I guess this "feature" (returning default values for not nullable
columns that contain null) must have been implemented with the best
goodwill, yet it's a pesterer.
Ciao
--
Nando Dessena
http://www.flamerobin.org
AdSF> There is another problem related with DEFAULT and GEN_ID.
AdSF> If you have a NOT NULLable field and alter a column to have a DEFAULT
AdSF> with GEN_ID, records stored in the previous format will evaluate the
AdSF> DEFAULT clause in each fetch and the generator will be incremented.
AdSF> This is at least strange.
yep. And the same goes with "DEFAULT CURRENT_TIMESTAMP" and the like.
Every time you have a non-constant or non-deterministic default
expression, actually. It's not strange, it's plain crazy.
I guess this "feature" (returning default values for not nullable
columns that contain null) must have been implemented with the best
goodwill, yet it's a pesterer.
Ciao
--
Nando Dessena
http://www.flamerobin.org