The fault or misunderstanding is probably mine, but:
I thought the "identity" definition was functionally the same as the
before-insert with generator. Particularly with regards to handling null
values during inserts. However, given:
create table TEST1 (
TEST_ID integer generated by default as identity primary key
TEST_NAME varchar(10)
);
Attempting to execute:
update or insert into TEST1 (TEST_ID, TEST_NAME)
values (null, 'abc') matching (TEST_ID)
results in:
validation error for column "TEST1"."TEST_ID", value "*** null ***".
However, the same query works without issue with a before-insert trigger
using a generator. My question - is this intended behavior? Or a bug in
the identity implementation?
--
Daniel
------------------------------------
------------------------------------
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Visit http://www.firebirdsql.org and click the Documentation item
on the main (top) menu. Try FAQ and other links from the left-side menu there.
Also search the knowledgebases at http://www.ibphoenix.com/resources/documents/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
------------------------------------
Yahoo Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/firebird-support/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/firebird-support/join
(Yahoo! ID required)
<*> To change settings via email:
firebird-support-dig...@yahoogroups.com
firebird-support-fullfeatu...@yahoogroups.com
<*> To unsubscribe from this group, send an email to:
firebird-support-unsubscr...@yahoogroups.com
<*> Your use of Yahoo Groups is subject to:
https://info.yahoo.com/legal/us/yahoo/utos/terms/
