org.jooq

Interface DivideByOnConditionStep

All Superinterfaces:

DivideByReturningStep

public interface DivideByOnConditionStep
extends DivideByReturningStep

An intermediate type for the construction of a relational division. This type can be used as a convenience type for connecting more conditions.

Author:

Lukas Eder

Method Summary

Methods

Modifier and Type	Method and Description
DivideByOnConditionStep	and(Condition condition) Combine the currently assembled conditions with another one using the Operator.AND operator.
DivideByOnConditionStep	and(String sql) Combine the currently assembled conditions with another one using the Operator.AND operator.
DivideByOnConditionStep	and(String sql, Object... bindings) Combine the currently assembled conditions with another one using the Operator.AND operator.
DivideByOnConditionStep	and(String sql, QueryPart... parts) Combine the currently assembled conditions with another one using the Operator.AND operator.
DivideByOnConditionStep	andExists(Select<?> select) Combine the currently assembled conditions with an EXISTS clause using the Operator.AND operator.
DivideByOnConditionStep	andNot(Condition condition) Combine the currently assembled conditions with a negated other one using the Operator.AND operator.
DivideByOnConditionStep	andNotExists(Select<?> select) Combine the currently assembled conditions with a NOT EXISTS clause using the Operator.AND operator.
DivideByOnConditionStep	or(Condition condition) Combine the currently assembled conditions with another one using the Operator.OR operator.
DivideByOnConditionStep	or(String sql) Combine the currently assembled conditions with another one using the Operator.OR operator.
DivideByOnConditionStep	or(String sql, Object... bindings) Combine the currently assembled conditions with another one using the Operator.OR operator.
DivideByOnConditionStep	or(String sql, QueryPart... parts) Combine the currently assembled conditions with another one using the Operator.OR operator.
DivideByOnConditionStep	orExists(Select<?> select) Combine the currently assembled conditions with an EXISTS clause using the Operator.OR operator.
DivideByOnConditionStep	orNot(Condition condition) Combine the currently assembled conditions with a negated other one using the Operator.OR operator.
DivideByOnConditionStep	orNotExists(Select<?> select) Combine the currently assembled conditions with a NOT EXISTS clause using the Operator.OR operator.

Methods inherited from interface org.jooq.DivideByReturningStep

returning, returning

Method Detail

and

@Support
DivideByOnConditionStep and(Condition condition)

Combine the currently assembled conditions with another one using the Operator.AND operator.

and

@Support
DivideByOnConditionStep and(String sql)

Combine the currently assembled conditions with another one using the Operator.AND operator.

NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!

See Also:

Factory.condition(String)

and

@Support
DivideByOnConditionStep and(String sql,
                                  Object... bindings)

Combine the currently assembled conditions with another one using the Operator.AND operator.

NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!

See Also:

Factory.condition(String, Object...)

and

@Support
DivideByOnConditionStep and(String sql,
                                  QueryPart... parts)

Combine the currently assembled conditions with another one using the Operator.AND operator.

NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!

See Also:

Factory.condition(String, QueryPart...)

andNot

@Support
DivideByOnConditionStep andNot(Condition condition)

Combine the currently assembled conditions with a negated other one using the Operator.AND operator.

andExists

@Support
DivideByOnConditionStep andExists(Select<?> select)

Combine the currently assembled conditions with an EXISTS clause using the Operator.AND operator.

andNotExists

@Support
DivideByOnConditionStep andNotExists(Select<?> select)

Combine the currently assembled conditions with a NOT EXISTS clause using the Operator.AND operator.

or

@Support
DivideByOnConditionStep or(Condition condition)

Combine the currently assembled conditions with another one using the Operator.OR operator.

or

@Support
DivideByOnConditionStep or(String sql)

Combine the currently assembled conditions with another one using the Operator.OR operator.

NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!

See Also:

Factory.condition(String)

or

@Support
DivideByOnConditionStep or(String sql,
                                 Object... bindings)

Combine the currently assembled conditions with another one using the Operator.OR operator.

NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!

See Also:

Factory.condition(String, Object...)

or

@Support
DivideByOnConditionStep or(String sql,
                                 QueryPart... parts)

Combine the currently assembled conditions with another one using the Operator.OR operator.

NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!

See Also:

Factory.condition(String, QueryPart...)

orNot

@Support
DivideByOnConditionStep orNot(Condition condition)

Combine the currently assembled conditions with a negated other one using the Operator.OR operator.

orExists

@Support
DivideByOnConditionStep orExists(Select<?> select)

Combine the currently assembled conditions with an EXISTS clause using the Operator.OR operator.

orNotExists

@Support
DivideByOnConditionStep orNotExists(Select<?> select)

Combine the currently assembled conditions with a NOT EXISTS clause using the Operator.OR operator.