Addendum: Of course, you can work around this problem already now, by explicitly forcing jOOQ to use inline values: http://www.jooq.org/doc/3.0/manual/sql-building/bind-values/inlined-parameters/
Cheers Lukas 2013/3/17 Lukas Eder <[email protected]> > Hello, > > Yes, there are such limitations in various SQL dialects: > https://github.com/jOOQ/jOOQ/issues/1520 > > The solution is to detect the number of bind values at render time, and > inline them, once the respective limit has been reached. So far, I wasn't > quite sure how to implement this fix optimally. Probably, upon reaching the > limit, the SQL statement has to be re-rendered... > > I'll increase the priority of this issue. > > Cheers > Lukas > > > 2013/3/17 Matthias Fuchs <[email protected]> > >> Hi guys, >> >> some time ago I found out that the mssql jdbc driver only supports up to >> 2100 paramers in a prepared statement. >> Sometimes I reach this limit, e.g when filling an WHERE IN clause. It >> would be nice if jooq would transparently split up the query into several >> queries. >> Currently I'm having this problem while batch deleting: >> * >> * >> *exe.delete(TABLE).where(TABLE.ID.in(List<String>)).execute()* >> >> -- >> 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/groups/opt_out. >> >> >> > > -- 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/groups/opt_out.
