Skip to content

Unlike other SQL-related sliced test annotations, @JooqTest does not auto-configure a test database #42371

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed
wilkinsona opened this issue Sep 19, 2024 · 2 comments
Labels
status: invalid An issue that we don't feel is valid type: bug A general bug

Comments

@wilkinsona
Copy link
Member

See #42360 for background.

While I consider this to be a bug, fixing it will result in a change in Boot's default behavior. As such, I think we should only fix it in a minor release rather than a maintenance release.

@vpavic
Copy link
Contributor

vpavic commented Sep 19, 2024

First off, it cannot be a bug since the behavior is explicitly called out in both @JooqTest javadoc and reference manual.

Secondly, as someone who primarily uses jOOQ for data access over the last couple of years, let me emphasize that jOOQ is about embracing SQL and native/vendor specific capabilities of used RDMBS translates into strong preference for integration testing against a real database. From that standpoint, this change would be a significant degradation of developer experience.

@wilkinsona
Copy link
Member Author

Thanks for the reminder, I'd forgotten that. This arrangement came about as a result of this discussion and some polishing. Let's keep things as they are.

@wilkinsona wilkinsona closed this as not planned Won't fix, can't repro, duplicate, stale Sep 19, 2024
@wilkinsona wilkinsona removed this from the 3.4.x milestone Sep 19, 2024
@wilkinsona wilkinsona added the status: invalid An issue that we don't feel is valid label Sep 19, 2024
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
status: invalid An issue that we don't feel is valid type: bug A general bug
Projects
None yet
Development

No branches or pull requests

2 participants