"Version" column should default to "managed = true"
---------------------------------------------------
Key: TUSCANY-835
URL: http://issues.apache.org/jira/browse/TUSCANY-835
Project: Tuscany
Issue Type: Improvement
Components: Java DAS RDB
Affects Versions: Java-Mx
Reporter: Kevin Williams
Fix For: Java-Mx
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
