[ http://issues.apache.org/jira/browse/DERBY-100?page=comments#action_12361121 ]
Daniel John Debrunner commented on DERBY-100: --------------------------------------------- OK - the coffee has kicked in and I understand the allow null comment in the spec. I'd forgotten that nullable meant a default of NULL, so compiling a truth table made it clear. Each column in the insert row that does not allow null as a value and does not have a default value must be given a value using the appropriate update method. nullable has default no no needs user supplied value (enforced by engine, exception) no yes no user supplied value needed (handled by engine, set to default) yes no no user supplied value needed (handled by engine, set to null) yes yes no user supplied value needed (handled by engine, set to default) So I believe that this code does not implement the spec correctly, in the case of no user supllied values. > Add support for insert functionality using JDBC 2.0 updatable resultset apis > ---------------------------------------------------------------------------- > > Key: DERBY-100 > URL: http://issues.apache.org/jira/browse/DERBY-100 > Project: Derby > Type: New Feature > Components: JDBC > Versions: 10.1.1.0 > Reporter: Mamta A. Satoor > Assignee: Fernanda Pizzorno > Attachments: DERBY-100.diff, DERBY-100.stat > > The JDBC 2.0 API introduced the ability to update/delete/insert rows from a > resultset using methods in the Java programming language rather than having > to send an SQL command. This Jira entry is to track the insert rows > functionality using JDBC 2.0 apis. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
