Lukas, we are using jTDS for historical reasons. The development of our software product goes back to 2010. On those days the JDBC driver from Microsoft wasn't as fast as nowadays and significantly slower than the jTDS driver (some rough testing seems to prove that jTDS is still a bit faster). But in general our product can run with any JDBC driver, hence with the one from Microsoft, too. In fact our product should run with any database, not only SQL Server, but also with MySQL, Oracle, DB2, etc. which is the reason we try to stick to ANSI-SQL in most cases and let the JDBC driver choose the best technique to execute the SQL statement we have written in code.
Your suggestion is quite interesting. Is that something the developer writing the SQL must be aware of or is jOOQ smart enough to apply this pattern if the target database is SQL Server (of a version that supports it) and the SQL contains large sets of parameters (as in my example)? Kind regards, Marcus -- 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.
