Andrus Adamchik <andru..bjectstyle.org> wrote:
> Or can we? I hate to change DataNode flow too much because of this. I
> think we should partition UPDATES with different NULL positions into
> separate queries at ContextCommit level.
>
> To make things more simple... Do we really care to support true batch
> updates for the queries that are using locking? If not, we can generate
> a single update query per row for the case above and also stop worrying
> about generic batch support.
>
> My take on it is that while INSERT and DELETE batches are quiet useful,
> UPDATE batches have very small size in most cases anyway. Anyone can
> think of a common scenario when there is a need to update a large
> number of objects at the same time (and with optimistic locking) that
> fit in the same query batch template?
I couldn't think of any case where my own projects do anything other than
single-item updates, which is why I didn't put much work into supporting
update batches for non-oracle drivers.
-Mike
This archive was generated by hypermail 2.0.0 : Sat Mar 20 2004 - 21:04:48 EST