java.lang.Object | |
↳ | com.atlassian.jira.database.SqlPredicates |
Additional query predicates not provided directly by QueryDSL
Constants | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
int | MAX_SQL_SERVER_PARAMETER_LIMIT | The maximum number of parameters SQL Server allows in a single query |
Public Constructors | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Public Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Create a
left in right or... expression for each list
This method can be removed once we upgrade to QueryDSL 3.6.0 or above, when QueryDSL introduces ExpressionUtils.inAny() | |||||||||||
Create a SQL IN clause, if necessary partitioning to account for Oracle's maximum of 1000 parameters for each IN clause.
|
[Expand]
Inherited Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
From class java.lang.Object |
The maximum number of parameters SQL Server allows in a single query
Create a left in right or...
expression for each list
This method can be removed once we upgrade to QueryDSL 3.6.0 or above, when QueryDSL introduces ExpressionUtils.inAny()
left | expression |
---|
left in right or...
expression
Create a SQL IN clause, if necessary partitioning to account for Oracle's maximum of 1000 parameters for each IN clause.
For Oracle, where the collection has greater than 1000 parameters, the clause will be partitioned into multiple IN...OR...IN clauses.
For other databases, a standard IN clause will be created.
This method can be removed once we upgrade to QueryDSL 3.6.0 or above, when QueryDSL will split large IN clauses for us. See https://github.com/querydsl/querydsl/issues/1022left | left value |
---|---|
right | right collection |