You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Rick Hillegas (JIRA)" <ji...@apache.org> on 2014/01/09 16:58:53 UTC
[jira] [Commented] (DERBY-6453) Remove dead code in InsertResultSet
and flag skipCheckConstraints
[ https://issues.apache.org/jira/browse/DERBY-6453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13866733#comment-13866733 ]
Rick Hillegas commented on DERBY-6453:
--------------------------------------
Linking to DERBY-532, since this investigation was kicked off by implementing support for deferrable CHECK constraints.
> Remove dead code in InsertResultSet and flag skipCheckConstraints
> -----------------------------------------------------------------
>
> Key: DERBY-6453
> URL: https://issues.apache.org/jira/browse/DERBY-6453
> Project: Derby
> Issue Type: Improvement
> Components: SQL
> Reporter: Dag H. Wanvik
> Assignee: Dag H. Wanvik
> Priority: Minor
> Attachments: cleanup-misc-2.diff, cleanup-misc-2.stat, cleanup-misc.diff, cleanup-misc.stat
>
>
> I identified some unused code; a flag that is always false, and code for handling triggers in bulk insert which is unused (by inspection and corroborated by JaCoCo results for our regression tests): we disable bulk insert if there are triggers present, cf.
> * DMLModStatementNode#getAllRelevantTriggers ->
> adjustDeferredFlag(true)
> * InsertResultSet#bulkInsert:
> bulkInsert = verifyBulkInsert()->
> :
> // bulk insert is disabled for deferred mode inserts
> if (constants.deferred)
> return false;
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)