This is fine with me. Most of the time users will probably want to have the DAS do the work rather than manually updating the version column or having a database trigger do it.
Brent On 10/12/06, Kevin Williams <[EMAIL PROTECTED]> wrote:
While writing the User level documentation for Optimistic Concurrency Control I started wondering about our current default which is to NOT manage the designated version column. That is, we assume that it is the client's responsibility to modify this column whenever they modify any other column in the associated row. We also provide another option in which the DAS is responsible for bumping the value of the designated column whenever any other column is modified in the associated row. It seems to me that this will be the typical case and should also be the default to save the developer from specifying another piece of config. If there are no strong feelings otherwise then I will open a JIRA for this. Thanks. -- Kevin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
