>> Hmm, yes I roughly remember having seen this before when writing >> relevant integration tests. Maybe, my integration tests just skip this >> part for Sybase ASE. So how would this be resolved? By replacing bind >> values by inline values in generated SQL? Can it even be resolved? > > > We're not aware of a solution. I think the first step would be a unit test > followed by a question on stackoverflow.com :-)
Yes, funny. My relevant integration test contains a comment related to this, testLargeINCondition() in https://github.com/lukaseder/jOOQ/blob/master/jOOQ-test/src/org/jooq/test/_/testcases/PredicateTests.java I've already tried reaching the max number of bind values for SQL Server 2008 R8 (2100), and ASE 15.5 (2000). Here's the Stack Overflow question related to this topic: http://stackoverflow.com/questions/11266609/how-to-circumvent-the-maximum-number-of-bind-values-for-sybase-ase-and-sql-serve I assume that inlining of bind variables is the only option... But let's see N.B: I've just now discovered a troubling bug related to the splitting of large NOT IN condition, which isn't done correctly by jOOQ: https://sourceforge.net/apps/trac/jooq/ticket/1515 Cheers Lukas
