[
https://issues.apache.org/jira/browse/TORQUE-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Fox resolved TORQUE-233.
-------------------------------
Resolution: Fixed
Fix Version/s: 4.0-beta2
Assignee: Thomas Fox
Deadlock detection does not work for hsqldb, I have not been able to produce a
deadlock detected by hsqldb, the classical case for table-based locking(write
table 1 transaction1, write table 2 in transaction 2, write teable 2 in
transaction 1, write table1 in transaction 2) just waits indefinitely with no
deadlock detected.
Everything else works.
> Exception translation
> ---------------------
>
> Key: TORQUE-233
> URL: https://issues.apache.org/jira/browse/TORQUE-233
> Project: Torque
> Issue Type: Wish
> Components: Runtime
> Affects Versions: 4.0-beta1
> Reporter: Thomas Fox
> Assignee: Thomas Fox
> Fix For: 4.0-beta2
>
>
> Currently, there is no portable way to determine the reason of an Exception.
> E.g. if an exception occurs during saving, it could be due to a unique key
> violation.
> It would be nice such a Violation would result in a special subclass of
> TorqueException, so the reason could be determined in a way portable across
> databasess
> (Currently one can look at the root cause of the Torque exception and then
> e.g. form ysql check whether it's a
> MySQLIntegrityConstraintViolationException, but of course this is not
> portable across databases)
--
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: [email protected]
For additional commands, e-mail: [email protected]
