| | O/R mappers and concurrency control |
 | | This means that, besides the point that there is no silver bullet to solve all concurrency problems, it is also not possible to define a common way to supply concurrency control: different developers will implement concurrency control differently, or at least: want to use it differently. |
 | | Concurrency control as flexible as you can possibly get, and usable not only on a per-type basis but also on a per-instance basis. |
 | | If you want higher level concurrency functionality, it is not wise to implement that on a low level, so it's in all cases more wise to simply add logic which prevents low level concurrency violations pop up like multi-edits of the same row. |
| weblogs.asp.net /fbouma/archive/2004/03/06/85125.aspx (1741 words) |