[nhibernate-issues] [JIRA] Commented: (NH-789) ORA-08177 not wrapped as StaleObjectException with Oracle.DataAcess

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-789?page=comments#action_14277 ]
     
Sergey Koshcheyev commented on NH-789:
--------------------------------------

Then just change from type="Timestamp" to type="DateTime" if you don't need the milliseconds. The exception has nothing to do with NHibernate, looks like Oracle does its own locking or something. NHibernate only throws StaleStateException if the count of rows affected by UPDATE/INSERT don't match what it expects, this functionality doesn't rely on Oracle errors, these are different things.

> ORA-08177 not wrapped as StaleObjectException with Oracle.DataAcess
> -------------------------------------------------------------------
>
>          Key: NH-789
>          URL: http://jira.nhibernate.org/browse/NH-789
>      Project: NHibernate
>         Type: Bug
>   Components: Core
>     Versions: 1.0.2
>     Reporter: Johannes Schmidt

>
> The OracleClientDriver does not support milliseconds for Timestamp mapping. So, I decided to used OracleDataClientDriver. I'm using OptimisticLock settings in the mapping file. If there is a concurrency problem, I except a StaleObjectException, but the ADOExceptionReporter throws an exceptions that contains only the text of the Oracle exception for ORA-08177.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.nhibernate.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira