It's worth supporting as a built-in, and it may be currently possible
as a workaround to simply subclass the query and set
isUsingOptimisticLocking() to always return false.
Open a Jira issue. I can't say when I'll get around to it on my own,
so a patch would speed things up (my thoughts are another boolean flag
on query: willUseOptimisticLocking()? that's true by default).
On 8/29/05, Gili <cowwo..bs.darktech.org> wrote:
> Hi,
>
> I'd like a *Query to use the default optimistic locking setting
> *unless* I override it at the Query level. So for example, optimistic
> locking is on by default on field "name" but for this one specific query
> I want to disable it.
>
> In my case, I want to delete a record from the underlying database
> regardless of whether the underlying instance was modified or not. I
> know I can use SQLTemplate as always but it would be much nicer if I
> could configure this directly into a NonSelectingQuery or something.
> What do you think?
>
> Gili
> --
> http://www.desktopbeautifier.com/
>
This archive was generated by hypermail 2.0.0 : Mon Aug 29 2005 - 14:32:51 EDT