db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (JIRA)" <j...@apache.org>
Subject [jira] Created: (DERBY-4538) If the CREATE TRIGGER does not have the REFERENCING clause, then there is no need to keep before and after values
Date Fri, 05 Feb 2010 06:32:27 GMT
If the CREATE TRIGGER does not have the REFERENCING clause, then there is no need to keep before
and after values 
------------------------------------------------------------------------------------------------------------------

                 Key: DERBY-4538
                 URL: https://issues.apache.org/jira/browse/DERBY-4538
             Project: Derby
          Issue Type: Improvement
          Components: SQL
    Affects Versions: 10.6.0.0
            Reporter: Mamta A. Satoor
            Priority: Minor


In order for the trigger action to have access to before and after values of the triggering
table, the CREATE TRIGGER should use the REFERENCING clause. Without the REFERENCING clause,
old and new values of triggering table can't be accessed by the trigger action. Based on this,
we can improve Derby memory utilization by not keeping old and new values if REFERENCING clause
is missing. It will be good to see if the code already does this optimization and if not,
then introducing this optimization will definitely be very useful when the triggering table
could have LOB columns.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message