db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4136) Allow optimizer overrides for UPDATE and DELETE
Date Sun, 13 Jun 2010 21:35:14 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878436#action_12878436
] 

Dag H. Wanvik commented on DERBY-4136:
--------------------------------------

I found the same is true for update, so I will try to find out why this has been disabled
for DELETE and UPDATE. Maybe it's not working reliably for all statements..

> 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.


Mime
View raw message