-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
promote jakarta.persistence.database-xxxx config properties #628
Labels
candidate-for-4
Good candidate for JPA 4
Comments
Hibernate will use |
Yes, exactly, that's what I'm trying to say. |
gavinking
added a commit
to gavinking/persistence
that referenced
this issue
Sep 20, 2024
see issue jakartaee#628 Signed-off-by: Gavin King <[email protected]>
gavinking
added a commit
to gavinking/persistence
that referenced
this issue
Sep 20, 2024
see issue jakartaee#628 Signed-off-by: Gavin King <[email protected]>
gavinking
added a commit
to gavinking/persistence
that referenced
this issue
Sep 20, 2024
see issue jakartaee#628 Signed-off-by: Gavin King <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The configuration properties
jakarta.persistence.database-product-name
,jakarta.persistence.database-major-version
, andjakarta.persistence.database-minor-version
are currently defined as part of the container/provider contract.But these properties are generally-useful as a way of configuring the persistence provider when access to JDBC metadata is not available at startup time (for example, in Quarkus, or in some cloud environments). And so Hibernate has never treated them as specific to container-based configuration.
We should promote these to the same status as other application-settable config properties, and add them to
PersistenceConfiguration
.The text was updated successfully, but these errors were encountered: