You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafodion.apache.org by "RuoYu Zuo (JIRA)" <ji...@apache.org> on 2015/12/21 07:24:46 UTC
[jira] [Created] (TRAFODION-1716) Whole batch failed if there's
individual row referencing non-existing foreign key value to insert into
table.
RuoYu Zuo created TRAFODION-1716:
------------------------------------
Summary: Whole batch failed if there's individual row referencing non-existing foreign key value to insert into table.
Key: TRAFODION-1716
URL: https://issues.apache.org/jira/browse/TRAFODION-1716
Project: Apache Trafodion
Issue Type: Bug
Components: sql-exe
Reporter: RuoYu Zuo
Normally, when use JDBC/ODBC to do a rowset/batch insert into a table, if there's illegal/invalid value in some individual row in the batch, that row should just be dumped, and the rest of the batch shall be inserted successfully. But now, SQL just fails the entire batch, not even a single row can be inserted, if there's invalid referencing value as foreign from other table.
Actually for now, according to my tests, this happens to all conditions like there's constraint in the object table, and there's value in the batch violates the constraint, then the whole batch fails. See JIRA 1701, which describes the duplicate failure of a batch insert.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)