db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rick Hillegas <rick.hille...@oracle.com>
Date Mon, 19 Dec 2011 20:47:54 GMT
On 12/19/11 12:24 PM, JulioSerje wrote:
> Rick Hillegas-3 wrote:
>> On 12/16/11 1:42 PM, JulioSerje wrote:
>>> Is there any way to implement an update using a JOIN?  The reference
>>> manual
>>> only allows for one table to be updated:
>>> UPDATE table-Name [[AS] correlation-Name]
>>>     SET column-Name = Value
>>>     [ , column-Name = Value} ]*
>>>     [WHERE clause]
>>> We have an application where need to run many queries like:
>>> update t1  set t1.a=t2.b, t1.c=t2.d,...t1.x=(t2.a+t2.b/t2.y)
>>>          from Table1 t1 join Table2 t2 on t1.k=t2.k
>>>          where t1.x=1  and t2.y=2
>>> We offer support on our app to most data platforms (Oracle, MySql,
>>> SQLServer, PostgreSQL, SQLite, even Access..) and in all of them there is
>>> a
>>> way of doing this...
>>> Is this something missing in Derby?
>>> Any ideas highly appreciated.
>> Hi Julio,
>> UPDATE...FROM is a useful statement which appears in many SQL dialects.
>> However, it does not appear in the standard ANSI/ISO SQL dialect which
>> Derby implements, not even in the recently published 2011 version of the
>> standard dialect.
>> A standard approach to updating a column from a join is to use
>> subqueries in the SET clause. E.g., something like this:
>>       update t1 set a = ( select t2.a from t1, t2 where t1.b = t2.b );
>> Hope this helps,
>> -Rick
> Thanks a lot for your response, Rick.
> This, despite being a standard is a much cumbersome way of doing what in
> other dialects is straightforward. I believe this may be seen as a weakness
> of Derby engine (- and maybe of the standard itself).
>   A second question would be if performance of a 'standard' update with quite
> a few sub queries will be the same or comparable to an UPDATE ... FROM ...
> type of query. Does Derby internal optimizer recognize this situation?
Hi Julio,

I haven't looked into the details of what the Derby optimizer does in 
the case of multiple SET clauses, each driven by its own subselect. It 
is likely that this is an underoptimized case. If you rewrite your query 
to use subselects in the SET clauses, and you experience poor 
performance on Derby, you may be able to get advice on this list about 
how to improve that performance.

It is possible that the Derby UDPATE will compute different results than 
the UPDATE...FROM statements in your other databases. Derby may even 
raise an error. If Derby raises an error, this may be a warning to you 
that your UPDATE...FROM statements are ambiguous. An UPDATE...FROM 
statement may end up updating the same column multiple times in a 
non-deterministic way. This can happen if the join in the FROM clause 
returns multiple joined rows for each row in the table you are updating. 
In this situation, the standard syntax will raise an error because the 
subselects are supposed to return one row each. More information on this 
problem can be found here: 

Hope this is helpful,

View raw message