Feature #4015
upgrade to a newer Hibernate release
Status:
Rejected
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:
0%
billable:
No
vendor_id:
GCD
version:
Related issues
History
#1 Updated by Eric Faulhaber about 5 years ago
As documented here, we currently are at a customized version of 4.18. We last upgraded to this version ~6 years ago. The patches documented in that wiki will need to be ported to the newer version, to the degree Hibernate has not added an alternative and at least as effective way to achieve the custom support for which they were developed (e.g., temporary tables, custom HQL syntax, SQL generation fixes, etc.).
The reasons for upgrading to a newer Hibernate are to:
- keep current for the sake of any external development which must integrate with FWD using Hibernate; and
- take advantage of any improvements to the feature set and/or performance of Hibernate which may have been offered in the interim period since our last upgrade.
The exact target version of Hibernate is not yet determined.
#2 Updated by Eric Faulhaber about 5 years ago
- Related to Feature #4016: replace portions of Hibernate which are non-performant added
#3 Updated by Eric Faulhaber over 4 years ago
- Status changed from New to Rejected
We have decided to replace Hibernate with a bespoke ORM implementation instead.