[
https://issues.apache.org/jira/browse/DERBY-4136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878438#action_12878438
]
Dag H. Wanvik commented on DERBY-4136:
--------------------------------------
I went through the original writeup for DERBY-573 and the JIRA comments, but I
could not find a rationale that DELETE and UPDATE were exempted. Can anybody
remember if there was a reason?
> Allow optimizer overrides for UPDATE and DELETE
> -----------------------------------------------
>
> Key: DERBY-4136
> URL: https://issues.apache.org/jira/browse/DERBY-4136
> Project: Derby
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 10.4.2.0
> Reporter: Ronald Tschalaer
> Priority: Minor
>
> Since UPDATE and DELETE statements effectively run a query behind the scenes
> to find the rows to update or delete, it would be useful to be able specify
> optimizer overrides (-- DERBY-PROPERTIES) for these statements too. As a
> specific use case, I have an issue with locking where I need to ensure the
> indexes are always used in order to prevent deadlocks. The current workaround
> is to run a SELECT (where I can supply the appropriate --DERBY-PROPERTIES
> index=...) with an updatable ResultSet and do the updates/deletes on the
> ResultSet. While this works, it is uglier and less clear than the
> corresponding UPDATE/DELETE statements.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
