[
https://issues.apache.org/jira/browse/DERBY-4136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamta A. Satoor updated DERBY-4136:
-----------------------------------
Urgency: Normal
Labels: derby_triage10_10 (was: )
> 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
> Labels: derby_triage10_10
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
