-
Notifications
You must be signed in to change notification settings - Fork 158
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
Support for driver version 4.X #377
Comments
Hi, I'm sorry but it's too hard to maintain fongo alone, and drivers are moving too fast. In the same time, testcontainers is an awesome project and can handle all mongodb version. see https://phauer.com/2019/modern-best-practices-testing-java/#dont-use-in-memory-databases-for-tests for example |
2 similar comments
Hi, I'm sorry but it's too hard to maintain fongo alone, and drivers are moving too fast. In the same time, testcontainers is an awesome project and can handle all mongodb version. see https://phauer.com/2019/modern-best-practices-testing-java/#dont-use-in-memory-databases-for-tests for example |
Hi, I'm sorry but it's too hard to maintain fongo alone, and drivers are moving too fast. In the same time, testcontainers is an awesome project and can handle all mongodb version. see https://phauer.com/2019/modern-best-practices-testing-java/#dont-use-in-memory-databases-for-tests for example |
hi @twillouer , I am working on upgrade of Fongo to support driver version 4.X. I will be a very big PR and I wanted to ask if you will be willing to review and merge such PR? |
hi, thanks, yes, it will be possible :) |
@vladimirmyp are you working on the PR. We were also upgrading our mongo client version to 4.x and faced the same issue with fmongo. Seeing your comment I refrained to start working on it. |
There are situations with Quarkus where the driver version 4.X is absolutely necessary and this seems to be the most usable solution for handling unit testing with database connection beans.
The text was updated successfully, but these errors were encountered: