-
Notifications
You must be signed in to change notification settings - Fork 3k
Rename quarkus.hibernate-orm.database.generation to quarkus.hibernate-orm.schema-management.strategy #47252
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
Conversation
/cc @marko-bekhta (hibernate-search) |
🙈 The PR is closed and the preview is expired. |
* | ||
* Accepted values: `none`, `create`, `drop-and-create`, `drop`, `update`, `validate`. | ||
*/ | ||
@WithParentName |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
since it's generation.strategy
in the properties files, do we need to keep the @WithParentName
?
So... I'm all for renaming, but if we're going that route, we might want to plan for the other renamings that we might need later? See in particular this comment: #21866 (comment)
|
@yrodiere this is now ready! |
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks nice 🎉 !
only have that one question about using two properties at the same time (added inline)
persistenceUnitConfig.database().generation().generation() | ||
.orElse(persistenceUnitConfig.schemaManagement().strategy())); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So, if the user applies both, then the deprecated option will "win"?
maybe we should check how the two match (or new one is none) and fail ? (if so, the same would apply to other options in this config)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, we sure could. But I think it's going to be a bit annoying as you can't really know if the new config is set or not (if it's set to the default) if you don't make it optional.
And it makes dropping the old stuff a bit more painful.
But if you feel like it, feel free to build on it once this is in.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks. LGTM overall, but I think there's a small problem in dev service behavior...
.../src/main/java/io/quarkus/hibernate/orm/deployment/dev/HibernateOrmDevServicesProcessor.java
Outdated
Show resolved
Hide resolved
Also make sure we use .strategy instead of a @WithParentName property. This is part of an overall effort to make YAML configuration less confusing and avoid having to use `~`. Also related to: quarkusio#21866 (comment)
Status for workflow
|
This comment has been minimized.
This comment has been minimized.
Status for workflow
|
@gsmet Merged, thanks! Will you add something to the migration guide (and maybe |
Quickstarts updated quarkusio/quarkus-quickstarts#1528 |
@lucamolteni awesome, that was on my TODO list. I will prepare the entry in the migration guide and also the Quarkus Updates recipe. |
Also adjusted a couple of other properties in passing.
This is part of an overall effort to make YAML configuration less confusing and avoid having to use
~
.