[ http://issues.apache.org/jira/browse/DERBY-171?page=all ]
David Van Couvering resolved DERBY-171:
---------------------------------------
Resolution: Fixed
Patch built successfully, derbyall passed. Committed changes, revision 231366
> Need Correlation ID in UPDATE/DELETE statements
> -----------------------------------------------
>
> Key: DERBY-171
> URL: http://issues.apache.org/jira/browse/DERBY-171
> Project: Derby
> Type: Improvement
> Components: SQL
> Versions: 10.1.1.1
> Environment: Windows XP SP1 Professional
> Reporter: George Baklarz
> Assignee: Rick Hillegas
> Fix For: 10.1.1.1
> Attachments: bug171.diff, bug171.html
>
> You currently can't use a correlation ID in an UPDATE/DELETE statement. This
> makes it cumbersome to do the following:
> UPDATE EMPLOYEE_BONUS
> SET BONUS = (SELECT SUM(BONUSES.BONUS) FROM BONUSES WHERE
> EMPLOYEE_BONUS.EMPL_ID = BONUSES.EMPL_ID);
> The use of a correlation ID makes this easier to code.
> UPDATE EMPLOYEE E
> SET BONUS = (SELECT SUM(B.BONUS) FROM BONUSES B WHERE B.EMPL_ID =
> E.EMPL_ID);
> This is particularly important if you get carried away with long SCHEMA and
> TABLE names!
--
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
