Project:
| View Revisions: Issue #39163 | [ All Revisions ] [ Back to Issue ] | ||
| Summary | 0039163: QueryTimeoutException is no longer thrown in Oracle after Hibernate 5.3 upgrade | ||
| Revision | 2018-08-30 20:45 by AtulOpenbravo | ||
| Description | In case of exceptions thrown by triggers in Oracle before Hibernate upgrade they were thrown as QueryTimeoutException. However after Hibernate upgrade it is used GenericJDBCException instead (exactly the same as in PostgreSQL). In InventoryCountProcess there is a catch block that differentiate between PG and Oracle. After Hibernate upgrade there is no need to differentiate anymore, but also we need to make sure the exception message is properly thrown in both databases. Similar use of QueryTimeoutException could be also found in 1. VariantChDescUpdateProcess.java 2. VariantAutomaticGenerationProcess |
||
| Revision | 2018-08-21 21:05 by AtulOpenbravo | ||
| Description | In case of exceptions thrown by triggers in Oracle before Hibernate upgrade they were thrown as QueryTimeoutException. However after Hibernate upgrade it is used GenericJDBCException instead (exactly the same as in PostgreSQL). In InventoryCountProcess there is a catch block that differentiate between PG and Oracle. After Hibernate upgrade there is no need to differentiate anymore, but also we need to make sure the exception message is properly thrown in both databases. |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |