[
https://issues.apache.org/jira/browse/TORQUE-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13637696#comment-13637696
]
rajguru commented on TORQUE-281:
--------------------------------
Concurrent connection - I guess that's the reason there is a support for
version column in torque. Doesn't that solve the concurrency issue? This is
nothing to do with concurrency.
> Only issue SQL update with columns whose value is changed in dbObject, since
> it was loaded from db
> --------------------------------------------------------------------------------------------------
>
> Key: TORQUE-281
> URL: https://issues.apache.org/jira/browse/TORQUE-281
> Project: Torque
> Issue Type: Improvement
> Reporter: rajguru
> Assignee: Thomas Fox
>
> This means dbObject needs to have a way to see oldValue and newValue. If so
> also provide some hooks in the code before update/after update/before
> insert/after insert/before delete and after delete, so one can plugin an
> auditing code to log the oldValue to newValue change
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscr...@db.apache.org
For additional commands, e-mail: torque-dev-h...@db.apache.org
