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 de...@db.apache.org on 2004/09/29 20:56:32 UTC
[jira] Created: (DERBY-14) Triggers do not evaluate functions in VALUES trigger actions.
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/DERBY-14
Here is an overview of the issue:
---------------------------------------------------------------------
Key: DERBY-14
Summary: Triggers do not evaluate functions in VALUES trigger actions.
Type: Bug
Status: Unassigned
Priority: Minor
Project: Derby
Components:
SQL
Versions:
10.0.2.0
Assignee:
Reporter: Ramandeep Kaur
Created: Wed, 29 Sep 2004 11:54 AM
Updated: Wed, 29 Sep 2004 11:54 AM
Description:
Opening this bug on behalf of Jack Klebanoff.
---------------------------------------------------------
If a trigger is created with
CREATE TRIGGER T ... VALUES( fn())
The function fn is not called even if the trigger event
happens. Side effects of the function will not happen.
Derby does not allow CALL statements in trigger actions.
In Derby, one has to use a VALUES statement and depend on function side effects.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Resolved: (DERBY-14) Triggers do not evaluate functions in VALUES trigger actions.
Posted by "Jack Klebanoff (JIRA)" <de...@db.apache.org>.
[ http://nagoya.apache.org/jira/browse/DERBY-14?page=history ]
Jack Klebanoff resolved DERBY-14:
---------------------------------
Resolution: Fixed
Fix Version: 10.0.2.0
Fixed in Subversion revision 53829.
> Triggers do not evaluate functions in VALUES trigger actions.
> -------------------------------------------------------------
>
> Key: DERBY-14
> URL: http://nagoya.apache.org/jira/browse/DERBY-14
> Project: Derby
> Type: Bug
> Components: SQL
> Versions: 10.0.2.0
> Reporter: Ramandeep Kaur
> Priority: Minor
> Fix For: 10.0.2.0
>
> Opening this bug on behalf of Jack Klebanoff.
> ---------------------------------------------------------
> If a trigger is created with
> CREATE TRIGGER T ... VALUES( fn())
> The function fn is not called even if the trigger event
> happens. Side effects of the function will not happen.
> Derby does not allow CALL statements in trigger actions.
> In Derby, one has to use a VALUES statement and depend on function side effects.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Closed: (DERBY-14) Triggers do not evaluate functions in VALUES trigger actions.
Posted by "Jack Klebanoff (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-14?page=all ]
Jack Klebanoff closed DERBY-14:
-------------------------------
> Triggers do not evaluate functions in VALUES trigger actions.
> -------------------------------------------------------------
>
> Key: DERBY-14
> URL: http://issues.apache.org/jira/browse/DERBY-14
> Project: Derby
> Type: Bug
> Components: SQL
> Versions: 10.0.2.0
> Reporter: Ramandeep Kaur
> Priority: Minor
> Fix For: 10.0.2.0
>
> Opening this bug on behalf of Jack Klebanoff.
> ---------------------------------------------------------
> If a trigger is created with
> CREATE TRIGGER T ... VALUES( fn())
> The function fn is not called even if the trigger event
> happens. Side effects of the function will not happen.
> Derby does not allow CALL statements in trigger actions.
> In Derby, one has to use a VALUES statement and depend on function side effects.
--
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