>Another solution is to use trigger to update "Number of Time Modified
>(NOTM)" column in the table as ODD recommended and make
>castor to check before update.
>As for clustering environment it want help a lot in case of frequent
>updates by different cluster nodes.
If you only check the NOTM on records which you are writing, then again you
are only implementing the second ansi transaction isolation level (read
committed isolation level). Often this is good enough, but users of the
resulting library need to be well educated about the implications. Otherwise
there is a real risk of developing ugly, hard to replicate race condition
bugs.
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
