OPENJPA-2930 Implements UUID and GenerationType.UUID strategy #124
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.
Added UUID support, using binary storage when the pair database-jdbc driver supports it, and string storage otherwise.
Binary storage is implemented as an DbDictionary property, defaulting to false, and true for PostgreSQL, H2 and HSQL databases.
Generated UUID value is a type 4 uuid, and storage of string representation is made, per spec, using its canonical representation.
Tested new features agains Postgresql 13 to 17, H2 1 and H2 2, current UUID capable HSQLDB and previous UUID not capable HSQLDB, MariaDB lts and latest, MySQL lts and latest. Could not test against Oracle.
Please be kind with this one. I may have missed a lot.