Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Guess the driver from the extension selected
See original GitHub issueFrom @gsmet I was thinking last night about maybe having the possibility to not ask for the driver if we have only one JDBC driver present.
E.g. we could have a BuildItem created by each database extension and inject a list of them in either Agroal or the JPA processor and do some automatic things based on the number of elements we obtain.
We could also detect that we have none and throw a user-friendly error as we discussed.
It was just before going to sleep so maybe it’s just a dumb idea 😃.
The Hibernate extension would also need to change to listen to these and not require a driver property in the case of no persistence.xml
Issue Analytics
- State:
- Created 5 years ago
- Comments:15 (12 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Good point @machi1990 .
@victorl2 I think that would be great, thanks a lot for offering! But could you wait a little bit to start? @gsmet is currently finishing a significant rewrite of how the datasources are configured. He should be done in just some days, maybe next week, so probably best you wait a little to avoid a massive conflict.
I would like to start contributing with this issue, can i take it ?