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 "Dag H. Wanvik (JIRA)" <ji...@apache.org> on 2011/01/21 18:41:46 UTC
[jira] Assigned: (DERBY-4136) Allow optimizer overrides for UPDATE
and DELETE
[ https://issues.apache.org/jira/browse/DERBY-4136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik reassigned DERBY-4136:
------------------------------------
Assignee: (was: Dag H. Wanvik)
Unassigning myself, since I have not been working on this issue for a while.
> 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.