Row-locking and on-find read ahead strategy

[senthilcool]

Why doesn't the row locking of the CMP bean work if the bean is configured for on-find read ahead strategy?

I am able to make it work with the default or on-load startegies but in either case the container fires two queries for every update. The first query to get the primary key and the second one to get the remaining fields as a SELECT FOR UPDATE.

Is there way to make row locking work with just one query before the UPDATE statement ?

Thanks for the help.

[ioparra]

No.


Okay, a little bit more explanation. It appears that the row-locking strategy is only in place during ejbLoad stage of the CMP. Becuase of that, the finder has no knowledge of row-locking. This also invalidates the on-find loading strategy(it might as be on-load to save BW).

I guess row-locking a finder would be a nice feature to have. Dunno how much work is involved to make it work.
-Ivan

[senthilcool]

Ivan, thanks for the reply.