Hello,
> AFAIK, file locks are new to JDK 1.4 and the behivor can vary slightly on
> different platforms.
Yes, but you can use a fake file locking mechanism as long as the JBoss
server is the only one to use these files.
> As I understand it, select for update is used to get an exclusive lock on
> the data selected for the term of the transaction. This behivor is not
> always desireable. There are certain application that don't want any
> transaction isolation. Some want for example a last commited transaction
> updates the data. This can give you huge performance boost, at
> the risk of
> data corruption, which doesn't matter in some cases.
furthermore, it seems that some databases do not allow the "select .. for
update" when selecting on more than one table i.e. for example if the future
JBoss O/R mapping allows for an entity bean to have its data disseminated on
many tables (with one-to-one relationship between them)
Cheers,
Sacha
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
