[
https://issues.apache.org/jira/browse/DERBY-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502679
]
Myrna van Lunteren commented on DERBY-1102:
-------------------------------------------
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.
> Test triggerGeneral & triggerStream (at least) uses internal old api's
> related to triggers.
> -------------------------------------------------------------------------------------------
>
> Key: DERBY-1102
> URL: https://issues.apache.org/jira/browse/DERBY-1102
> Project: Derby
> Issue Type: Bug
> Components: SQL, Test
> Affects Versions: 10.2.1.6
> Reporter: Daniel John Debrunner
> Assignee: Daniel John Debrunner
> Priority: Minor
> Fix For: 10.3.0.0
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
