This message was deleted.
# general
s
This message was deleted.
a
k
I mean for spring boot. Native via avatica I am aware about
a
what is special about spring boot? Avatica driver is the standard JDBC implementation for Java. Any 3rd party library that speaks JDBC language and uses the Driver interface, should be able to connect to druid.
k
Well, spring boot comes with ORM, that pre constructs the query template. Also, the select query can be made, using java method names. https://www.javatpoint.com/spring-with-orm-frameworks
a
So you don't need a druid JDBC connector for java. The responsibility of that connector is to execute JDBC queries from a java application. That is something that Avatica driver already does and what you will use in your application as well. The custom implementation that is needed here is what jdbc queries get generated as developers use a higher-level abstraction and leave it to the framework to build the actual sql queries. This is where I believe the
Dialect
interface comes in. I wonder what happens if you just use Postgres dialect along with Avatica JDBC driver. You could also write an implementation of Dialect interface that works well with Druid. In some ways, it very similar to writing a dialect for tableau or a BI tool that auto-generates SQL queries as users work with a UI. P.S - This short analysis is based on cursory research about how spring boot ORM works.
k
Thank you so much Abhishek. I’ll definitely explore this. Will need about a week.