TomohitoNakayama wrote:
I concluded as next.
Thinking "GENERATED BY DEFAULT AS IDENTITY" is a kind of default,
returning not null value for that column does not cause problem.
On the contrast , returning null value for column of "GENERATED BY
DEFAULT AS IDENTITY"
may cause some inconsistency, because the column is a column with
special default value.
Well, a GENERATED ALWAYS AS IDENTITY column is also "a column with special
default value", and yet Derby currently returns null for the default of that
kind of column. So to make GENERATED BY DEFAULT columns match this behavior (by
returning null) is, I think, the most consistent thing.
On the other hand, I agree that a non-null string such as "GENERATED_BY_DEFAULT"
has its benefits, as well. Since no one else has commented one way or the
other, and since I think we should get this issue resolved sooner rather than
later, I think you can go ahead and do things the way you think is best.
So please feel free to make the change as you prefer, and to post the patch to
the list so we can proceed.
Thanks!
Army
