Hi Mohan, Thanks for your additional details.
That use-case is perfectly well aligned with jOOQ. You would be using jOOQ's plain SQL API to construct queries without using the code generator: https://www.jooq.org/doc/latest/manual/sql-building/plain-sql Do note that the plain SQL API is the part in the jOOQ API, which might expose SQL injection vulnerabilities as well. If in doubt, it's always a good idea to wrap identifiers in DSL.name(). See also: https://www.jooq.org/doc/latest/manual/sql-building/names Every jOOQ query is able to produce a SQL string and bind variables through Query.getSQL() and Query.getBindValues(), which can then be sent to some other execution API, like Spring JDBC Let me know if you have any questions about the above Best Regards, Lukas 2017-06-05 23:30 GMT+02:00 Mohan <[email protected]>: > Hi Lukas, > > Thanks for the reply. > > Yes, I would like to avoid the code generator to generate the Java classes > corresponding to the database tables. > > My Scenario is I have to write very big queries which are like 200 to 400 > lines queries having many with clauses. In these queries, I have to pass to > some parameters also. > > So I am trying to evaluate JOOQ to achieve the below > > > - Handling the SQL queries generation with some readable way. > - Avoid complex string generation along with parameters > - SQL Injection issues > - Generate the SQL and use the spring jdbc template > > > Regards, > Mohan > > On Monday, 5 June 2017 06:25:12 UTC-5, Lukas Eder wrote: >> >> Hi Mohan, >> >> Thank you very much for your enquiry, and for your interest in using jOOQ >> with Snowflake. >> >> Currently, we're not officially supporting the Snowflake database and it >> doesn't look like this will change any time soon, as we focus mostly on >> databases with significant market traction, e.g. the ones on top of this >> list: >> https://db-engines.com/en/ranking >> >> Nonetheless, in the past, users have been successful in using the jOOQ >> Open Source Edition with unsupported databases, depending on the complexity >> of the queries written. Some of the more SQL standard compliant dialects >> are PostgreSQL and HSQLDB. >> >> Would you mind explaining your idea of using jOOQ with POJO classes a >> little bit more? Do you mean, you'd like to avoid using the code generator? >> >> Best Regards, >> Lukas >> >> 2017-06-02 22:35 GMT+02:00 Mohan <[email protected]>: >> >>> Hi, >>> >>> If I want to use JOOQ just to write complex sql queries with >>> https://www.snowflake.net/ then what kind of license should be used? >>> Opensource is good? >>> >>> Also Can I use JOOQ to write queries directly with table and columns >>> names with having a pojo clases for it and read the data like jdbc way? >>> >>> Regards, >>> Mohan >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "jOOQ User Group" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- > You received this message because you are subscribed to the Google Groups > "jOOQ User Group" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
