Derby
  1. Derby
  2. DERBY-4538

If the CREATE TRIGGER does not have the REFERENCING clause, then there is no need to keep before and after values for the triggering table

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 10.6.1.0
    • Fix Version/s: 10.3.3.1, 10.4.2.1, 10.5.3.2, 10.6.1.0
    • Component/s: SQL
    • Labels:
      None
    • Bug behavior facts:
      Performance

      Description

      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.

      1. DERBY4538_NoReferencingClause_diff_v1.txt
        5 kB
        Mamta A. Satoor
      2. DERBY4538_NoReferencingClause_diff_v2.txt
        25 kB
        Mamta A. Satoor
      3. DERBY4538_NoReferencingClause_stat_v1.txt
        0.1 kB
        Mamta A. Satoor
      4. DERBY4538_NoReferencingClause_stat_v2.txt
        0.4 kB
        Mamta A. Satoor

        Issue Links

          Activity

          No work has yet been logged on this issue.

            People

            • Assignee:
              Mamta A. Satoor
              Reporter:
              Mamta A. Satoor
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development