org.jooq

Interface TableOnConditionStep

All Superinterfaces:

Adapter, AliasProvider<Table<Record>>, Attachable, Comparable<NamedQueryPart>, FieldProvider, NamedQueryPart, QueryPart, SchemaProvider, Serializable, Table<Record>, TableLike<Record>, Type<Record>

public interface TableOnConditionStep
extends Table<Record>

An intermediate (optional) type for the construction of a JOIN clause, where the join criteria is added using an ON clause (with a Condition. 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
TableOnConditionStep	and(Condition condition) Combine the currently assembled conditions with another one using the Operator.AND operator.
TableOnConditionStep	and(String sql) Combine the currently assembled conditions with another one using the Operator.AND operator.
TableOnConditionStep	and(String sql, Object... bindings) Combine the currently assembled conditions with another one using the Operator.AND operator.
TableOnConditionStep	and(String sql, QueryPart... parts) Combine the currently assembled conditions with another one using the Operator.AND operator.
TableOnConditionStep	andExists(Select<?> select) Combine the currently assembled conditions with an EXISTS clause using the Operator.AND operator.
TableOnConditionStep	andNot(Condition condition) Combine the currently assembled conditions with a negated other one using the Operator.AND operator.
TableOnConditionStep	andNotExists(Select<?> select) Combine the currently assembled conditions with a NOT EXISTS clause using the Operator.AND operator.
TableOnConditionStep	or(Condition condition) Combine the currently assembled conditions with another one using the Operator.OR operator.
TableOnConditionStep	or(String sql) Combine the currently assembled conditions with another one using the Operator.OR operator.
TableOnConditionStep	or(String sql, Object... bindings) Combine the currently assembled conditions with another one using the Operator.OR operator.
TableOnConditionStep	or(String sql, QueryPart... parts) Combine the currently assembled conditions with another one using the Operator.OR operator.
TableOnConditionStep	orExists(Select<?> select) Combine the currently assembled conditions with an EXISTS clause using the Operator.OR operator.
TableOnConditionStep	orNot(Condition condition) Combine the currently assembled conditions with a negated other one using the Operator.OR operator.
TableOnConditionStep	orNotExists(Select<?> select) Combine the currently assembled conditions with a NOT EXISTS clause using the Operator.OR operator.

Methods inherited from interface org.jooq.Table

as, crossJoin, crossJoin, crossJoin, crossJoin, divideBy, fullOuterJoin, fullOuterJoin, fullOuterJoin, fullOuterJoin, getIdentity, getName, getRecordType, getReferences, getReferencesTo, getSchema, join, join, join, join, join, leftOuterJoin, leftOuterJoin, leftOuterJoin, leftOuterJoin, naturalJoin, naturalJoin, naturalJoin, naturalJoin, naturalLeftOuterJoin, naturalLeftOuterJoin, naturalLeftOuterJoin, naturalLeftOuterJoin, naturalRightOuterJoin, naturalRightOuterJoin, naturalRightOuterJoin, naturalRightOuterJoin, pivot, pivot, rightOuterJoin, rightOuterJoin, rightOuterJoin, rightOuterJoin

Methods inherited from interface org.jooq.QueryPart

attach

Methods inherited from interface org.jooq.Adapter

internalAPI

Methods inherited from interface java.lang.Comparable

compareTo

Methods inherited from interface org.jooq.FieldProvider

getField, getField, getField, getFields, getIndex

Methods inherited from interface org.jooq.TableLike

asTable, asTable

Method Detail

and

@Support
TableOnConditionStep and(Condition condition)

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

and

@Support
TableOnConditionStep 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
TableOnConditionStep 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
TableOnConditionStep 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
TableOnConditionStep andNot(Condition condition)

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

andExists

@Support
TableOnConditionStep andExists(Select<?> select)

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

andNotExists

@Support
TableOnConditionStep andNotExists(Select<?> select)

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

or

@Support
TableOnConditionStep or(Condition condition)

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

or

@Support
TableOnConditionStep 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
TableOnConditionStep 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
TableOnConditionStep 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
TableOnConditionStep orNot(Condition condition)

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

orExists

@Support
TableOnConditionStep orExists(Select<?> select)

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

orNotExists

@Support
TableOnConditionStep orNotExists(Select<?> select)

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