db-torque-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Clemens Hahn (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (TORQUE-233) Exception translation
Date Mon, 15 Oct 2012 12:44:04 GMT

     [ https://issues.apache.org/jira/browse/TORQUE-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Clemens Hahn updated TORQUE-233:
--------------------------------

    Attachment: torque4-generatedClasses.jpg
    
> 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
>         Attachments: torque4-generatedClasses.jpg
>
>
> 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: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org


Mime
View raw message