true
Expression
with which to constrain the query. A function can be passed to begin a nested where statement.false
operator
and the value
left null as a shortcut for equals (e.g. where( "column", 1 ) == where( "column", "=", 1 ) ).false
Expression
can be passed as well. If a QueryBuilder or Function is passed, it will be used as a subselect expression.where
method will parameterize the value
passed. If you want to constrain a column to another column, use the whereColumn
method."="
constraint, you can use a shortcut and define the value as the second argument.value
.true
Expression
with which to constrain the query. A function can be passed to begin a nested where statement.false
operator
and the value
left null as a shortcut for equals (e.g. where( "column", 1 ) == where( "column", "=", 1 ) ).false
Expression
can be passed as well. If a QueryBuilder or Function is passed, it will be used as a subselect expression.true
Expression
with which to constrain the query. A function can be passed to begin a nested where statement.false
operator
and the value
left null as a shortcut for equals (e.g. where( "column", 1 ) == where( "column", "=", 1 ) ).false
Expression
can be passed as well. If a QueryBuilder or Function is passed, it will be used as a subselect expression.true
true
true
false
"and"
"and"
or "or"
. Avoid passing this parameter explicitly. Where possible use the andWhere
and orWhere
dynamic methods instead.false
false
true
true
true
false
"and"
"and"
or "or"
. Avoid passing this parameter explicitly. Where possible use the andWhere
and orWhere
dynamic methods instead.whereBetween
method with the negate
flag set to true
. See the documentation for whereBetween
for usage and examples.true
true
operator
and the value
left null as a shortcut for equals (e.g. where( "column", 1 ) == where( "column", "=", 1 ) ).false
false
"and"
"and"
or "or"
. Avoid passing this parameter explicitly. Where possible use the andWhere
and orWhere
dynamic methods instead.where
, when using "="
as the operator you can use a shorthand passing the second column in as the operator and leaving the second column null
.Expressions
can be passed in place of either column.true
false
"and"
"and"
or "or"
. Avoid passing this parameter explicitly. Where possible use the andWhere
and orWhere
dynamic methods instead.false
false
true
false
"and"
"and"
or "or"
. Avoid passing this parameter explicitly. Where possible use the andWhere
and orWhere
dynamic methods instead.whereExists
method with the negate
flag set to true
. See the documentation for whereExists
for usage and examples.true
false
Expression
can be passed as well. If a QueryBuilder or Function is passed, it will be used as a subselect expression.false
"and"
"and"
or "or"
. Avoid passing this parameter explicitly. Where possible use the andWhere
and orWhere
dynamic methods instead.true
false
Expression
can be passed as well. If a QueryBuilder or Function is passed, it will be used as a subselect expression.false
"and"
"and"
or "or"
. Avoid passing this parameter explicitly. Where possible use the andWhere
and orWhere
dynamic methods instead.true
true
Expressions
may be used in any place a value is used. Alternatively, a function or QueryBuilder instance can be passed in to be used as a subquery expression.false
"and"
"and"
or "or"
. Avoid passing this parameter explicitly. Where possible use the andWhere
and orWhere
dynamic methods instead.false
false
whereIn
can be a single value, a list of values, or an array of values.","
) delimiter.Expressions
can be freely mixed in with other values.whereExists
method performs better for you than a whereIn
with a subquery.true
true
Expressions
may be used in any place a value is used. Alternatively, a function or QueryBuilder instance can be passed in to be used as a subquery expression.false
"and"
"and"
or "or"
. Avoid passing this parameter explicitly. Where possible use the andWhere
and orWhere
dynamic methods instead.whereIn
method with the negate
flag set to true
. See the documentation for whereIn
for usage and examples.true
false
[]
false
"and"
"and"
or "or"
. Avoid passing this parameter explicitly. Where possible use the andWhere
and orWhere
dynamic methods instead.true
false
"and"
"and"
or "or"
. Avoid passing this parameter explicitly. Where possible use the andWhere
and orWhere
dynamic methods instead.false
false
true
false
"and"
"and"
or "or"
. Avoid passing this parameter explicitly. Where possible use the andWhere
and orWhere
dynamic methods instead.false
false
onMissingMethod
to provide a few different helpers when working with where...
methods.where...
method in qb can be called prefixed with either and
or or
. Doing so will call the original method using the corresponding combinator.where
that does not match an existing qb method, qb will instead call the where
method using the rest of the method name as the first column name. (The rest of the arguments will be shifted to account for this.) This also applies to andWhere{Column}
and orWhere{Column}
method signatures.