Derby
  1. Derby
  2. DERBY-1102

Test triggerGeneral & triggerStream (at least) uses internal old api's related to triggers.

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 10.2.1.6
    • Fix Version/s: None
    • Component/s: SQL, Test
    • Urgency:
      Low

      Description

      Test uses the methods of TriggerExecutionContext to displat information about the tirgger. These are old non-standard and non-public interfaces from the old Cloudscape product. Tests should be re-written to not use such interfaces, only publshed interfaces which is all SQL for triggers.
      Methods on TriggerExecutionContext that are no longer required should be removed.

        Activity

        Hide
        Kathey Marsden added a comment -

        Unassigning due to inactivity. Some work was done. It would be good to evaluate what work remains on this issue.

        Show
        Kathey Marsden added a comment - Unassigning due to inactivity. Some work was done. It would be good to evaluate what work remains on this issue.
        Hide
        Dyre Tjeldvoll added a comment -

        This issue is targeted for 10.4, but has not been updated in 2008. Should the fix-version be changed/removed?

        Show
        Dyre Tjeldvoll added a comment - This issue is targeted for 10.4, but has not been updated in 2008. Should the fix-version be changed/removed?
        Hide
        Daniel John Debrunner added a comment -

        Unlikely to fix this for the 10.3 release

        Show
        Daniel John Debrunner added a comment - Unlikely to fix this for the 10.3 release
        Hide
        Myrna van Lunteren added a comment -

        Is this issue complete? Is more work in progress?
        If not, I'd like to take off the 10.3 fixin date. If a change happens after all before 10.3 the fixin can be set when the issue gets resolved.
        Although changes have gone in toward this, none of them would affect end-users, so no need to complete before 10.3.

        Show
        Myrna van Lunteren added a comment - Is this issue complete? Is more work in progress? If not, I'd like to take off the 10.3 fixin date. If a change happens after all before 10.3 the fixin can be set when the issue gets resolved. Although changes have gone in toward this, none of them would affect end-users, so no need to complete before 10.3.
        Hide
        Daniel John Debrunner added a comment -

        no plans to fix in 10.2.2

        Show
        Daniel John Debrunner added a comment - no plans to fix in 10.2.2
        Hide
        Rick Hillegas added a comment -

        Moving to 10.2.2.0.

        Show
        Rick Hillegas added a comment - Moving to 10.2.2.0.

          People

          • Assignee:
            Unassigned
            Reporter:
            Daniel John Debrunner
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:

              Development