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 "Daniel John Debrunner (JIRA)" <ji...@apache.org> on 2007/07/02 23:08:05 UTC
[jira] Updated: (DERBY-1102) Test triggerGeneral & triggerStream
(at least) uses internal old api's related to triggers.
[ https://issues.apache.org/jira/browse/DERBY-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel John Debrunner updated DERBY-1102:
-----------------------------------------
Fix Version/s: (was: 10.3.0.0)
10.4.0.0
Unlikely to fix this for the 10.3 release
> 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.4.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.