1. ColdFusion-ORM can be used with the cftransaction tag along with different isolationlevels (”read_uncommitted | read_committed | repeatable_read”). They work the same way as they do for cfquery stuff. See the ColdFusion 8 livedocs for an explanation of the different isolation levels.

2. Versioning properties can be defined for every persistent component which is one more way to handle conflict resolution and concurrency.

3. The attribute “optimistic-lock” can be defined in the persistent component with value that can be set to all or dirty or version or none.

For a detailed explanation on Versioning and optimistic-lock please refer “Versioning” and “Transaction and Concurrency” topics in ColdFusion documentation -> “Developing Applications with Adobe ColdFusion 9.pdf->Chapter 8: ColdFusion ORM”

I Look forward to more articles. I think Kevan has a very good question and am subscribing to the comments. In a nutshell, how does ColdFusion ORM handle conflict resolution for concurrent read/write?

I have a question on updates for multiple simultaneous requests. Can you explain what happens when multiple requests access the same record/object at the same time?

For example:
Request 1 reads a record
Request 2 reads a record
Request 1 updates the phone number of the record.
Request 2 access the phone number of the record

What phone number does request 2 see at this point? Does it see the original value stored in the database or the new value just set by request 1 (before the request ends).

Thanks, and I look forward to your next post!