Information could not effectively rely on any settings being available. State of settings and mapping information in the middle of that process. The venerable way to bootstrap Hibernate (build a SessionFactory) has been to use its Configuration class.Ĭonfiguration, historically, allowed users to iteratively add settings and mappings in any order and to query the Here are the big points: New bootstrap API Thanks to everyone who helped us get here with fixes, bug reports, suggestions,Ī lot of development has gone into 5.0. This has been a long time coming and is the result Today I have released Hibernate ORM 5.0 (5.0.0.Final). * - ModelBinder fails to bind version property when generated="always" * - Constraint name not considered for a Set while loading from XML mapping file * - Primary key not created for a Set after loading from XML mapping file * - SchemaManagementException when performing SchemaUpdate * - DefaultGeneratedValueTest fails on MySQL * - Change NameQualifierSupport for Hypersonic from CATALOG to SCHEMA * - NameQualifierSupport for Hypersonic should be catalog * - NPE in InformationExtractorJdbcDatabaseMetaDataImpl * - "stored" is a reserved keyword in MySQL 5.7 * - hbm2ddl tools cannot generate create/update script not modifying the database * - Incorrect splitting of string using dot as separator * - Throw MappingException when entity/component class defines multiple matching getters by stem name * - Reuse JAXBContext instance (Slow mapping initialization) - port HHH-10065 fix to 5.0 branch * - Hibernate ignores foreign-key name in hbm * - Using JPA 2.1 schema generation together with hbm2ddl runs into deadlock with MySQL * - scroll() and iterate() methods do not support provided HQLQueryPlan * - HQL Query with boolean and - EntityGraph applied to subquery when using collection function * - formula-based property leads to generation of invalid SQL with subselect fetches People without a Hibernate Jira account will not be able to access the previous link and can access the changelog in GitHub the issue I reported with Atlassian has been resolved and is ready for deployment into our hosted environment, I just do not know when that will happen.įor information on consuming the release via your favorite dependency-management-capable build tool, see įor those of you allergic to dependency-management-capable build tools, the release bundles can be obtained from SourceForge or BinTray. The complete list of changes can be found here. The really cool part is the amount of community help we have gotten in making that happen! Thanks to everyone responding, verifying and even fixing alot of these bugs! An additional 14 have been more properly reclassified as feature or enhancement requests rather than bugs. To date, 66 of those have been resolved - fixed or verified as out-of-date, unable-to-reproduce, etc. Initially that initiative pulled in roughly 750 issues. 20 of those came out of the recent Jira cleanup. There are 52 issues resolved in this release. The fourth bug-fix release for Hibernate ORM 5.0 Support has been added for specifying a batch size for write operations per Session. Support for using any JCache-compliant cache impl as a second-level caching provider. Its functionality being consumed into hibernate-core. That effectively means that the hibernate-entitymanager module no longer exists.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |