[OPENJPA-2940] Migration considerations for OpenJPA 4.2.0 (Jakarta Persistence 3.2) - #164
Open
rzo1 wants to merge 2 commits into
Open
[OPENJPA-2940] Migration considerations for OpenJPA 4.2.0 (Jakarta Persistence 3.2)#164rzo1 wants to merge 2 commits into
rzo1 wants to merge 2 commits into
Conversation
solomax
reviewed
Aug 27, 2026
…a Persistence 3.2) Documents the incompatibilities, default changes, platform/dependency requirements, database-specific changes, SPI changes and notable new features introduced by the Jakarta Persistence 3.2 implementation (#144), derived from the merged code changes and the PR review discussion.
Reverses the order of the top-level release sections in migration_considerations.xml so that the most recent release (OpenJPA 4.2.0) is listed first. Content is unchanged.
rzo1
force-pushed
the
jpa32-migration-considerations
branch
from
August 29, 2026 17:14
6e47f0e to
3d0a70f
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a
jpa_4.2section tomigration_considerations.xmlcovering the changes introduced by #144 (Jakarta Persistence 3.2), derived from the merged diff and the review discussion on that PR: platform and dependency requirements, JPQL/query semantics (new reserved identifiers, materializedgetResultList(), non-cascading bulkDELETE,FlushModeType.AUTO, rollback-only marking, argument validation), mapping and schema changes (default map key column, attribute overrides, converters, access type, generated DDL, schema generation), database-specific changes (PostgreSQL, MySQL/MariaDB, SQL Server, Oracle, HSQLDB), SPI changes and a compact list of notable new features.Each item states the previous and the new behaviour and, where one exists, the property that restores the old behaviour. The PostgreSQL
StoreCharsAsNumbersparagraph describes the behaviour after #163; the corresponding hunk in #163 should then be dropped, since it was placed under the OpenJPA 3.2.0 section.Draft: the section is long and some per-database / SPI subsections may deserve trimming — reviews welcome on what to keep.