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)" <de...@db.apache.org> on 2006/03/12 21:48:39 UTC
[jira] Created: (DERBY-1102) Test triggerGeneral (at least) uses
internal old api's related to triggers.
Test triggerGeneral (at least) uses internal old api's related to triggers.
---------------------------------------------------------------------------
Key: DERBY-1102
URL: http://issues.apache.org/jira/browse/DERBY-1102
Project: Derby
Type: Bug
Components: SQL, Test
Versions: 10.2.0.0
Reporter: Daniel John Debrunner
Assigned to: Daniel John Debrunner
Priority: Minor
Fix For: 10.2.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.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-1102) Test triggerGeneral & triggerStream
(at least) uses internal old api's related to triggers.
Posted by "Daniel John Debrunner (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (DERBY-1102) Test triggerGeneral (at least) uses
internal old api's related to triggers.
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1102?page=all ]
Rick Hillegas updated DERBY-1102:
---------------------------------
Fix Version/s: 10.2.2.0
(was: 10.2.1.0)
Moving to 10.2.2.0.
> Test triggerGeneral (at least) uses internal old api's related to triggers.
> ---------------------------------------------------------------------------
>
> Key: DERBY-1102
> URL: http://issues.apache.org/jira/browse/DERBY-1102
> Project: Derby
> Issue Type: Bug
> Components: SQL, Test
> Affects Versions: 10.2.1.0
> Reporter: Daniel John Debrunner
> Assigned To: Daniel John Debrunner
> Priority: Minor
> Fix For: 10.2.2.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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-1102) Test triggerGeneral (at least) uses
internal old api's related to triggers.
Posted by "Daniel John Debrunner (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1102?page=all ]
Daniel John Debrunner updated DERBY-1102:
-----------------------------------------
Fix Version/s: 10.3.0.0
(was: 10.2.2.0)
no plans to fix in 10.2.2
> Test triggerGeneral (at least) uses internal old api's related to triggers.
> ---------------------------------------------------------------------------
>
> Key: DERBY-1102
> URL: http://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
> Assigned To: 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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1102) Test triggerGeneral & triggerStream
(at least) uses internal old api's related to triggers.
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (DERBY-1102) Test triggerGeneral (at least) uses
internal old api's related to triggers.
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1102?page=all ]
Rick Hillegas updated DERBY-1102:
---------------------------------
Urgency: Low
> Test triggerGeneral (at least) uses internal old api's related to triggers.
> ---------------------------------------------------------------------------
>
> Key: DERBY-1102
> URL: http://issues.apache.org/jira/browse/DERBY-1102
> Project: Derby
> Issue Type: Bug
> Components: SQL, Test
> Affects Versions: 10.2.0.0
> Reporter: Daniel John Debrunner
> Assigned To: Daniel John Debrunner
> Priority: Minor
> Fix For: 10.2.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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-1102) Test triggerGeneral & triggerStream
(at least) uses internal old api's related to triggers.
Posted by "Dyre Tjeldvoll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dyre Tjeldvoll updated DERBY-1102:
----------------------------------
This issue is targeted for 10.4, but has not been updated in 2008. Should the fix-version be changed/removed?
> 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.
[jira] Assigned: (DERBY-1102) Test triggerGeneral & triggerStream
(at least) uses internal old api's related to triggers.
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden reassigned DERBY-1102:
-------------------------------------
Assignee: (was: Daniel John Debrunner)
Unassigning due to inactivity. Some work was done. It would be good to evaluate what work remains on this issue.
> 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
> Priority: Minor
> Fix For: 10.4.1.3
>
>
> 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.
[jira] Updated: (DERBY-1102) Test triggerGeneral & triggerStream
(at least) uses internal old api's related to triggers.
Posted by "Daniel John Debrunner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel John Debrunner updated DERBY-1102:
-----------------------------------------
Summary: Test triggerGeneral & triggerStream (at least) uses internal old api's related to triggers. (was: Test triggerGeneral (at least) uses internal old api's related to triggers.)
> 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
> Assigned To: 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.