Package org.jooq

Interface TableOnConditionStep<R extends Record>

All Superinterfaces:

Named, QueryPart, java.io.Serializable, Table<R>, TableLike<R>

public interface TableOnConditionStep<R extends Record>
extends Table<R>

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.

Referencing XYZ*Step types directly from client code

It is usually not recommended to reference any XYZ*Step types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql.

Drawbacks of referencing the XYZ*Step types directly:

• They're operating on mutable implementations (as of jOOQ 3.x)
• They're less composable and not easy to get right when dynamic SQL gets complex
• They're less readable
• They might have binary incompatible changes between minor releases

Author:

Lukas Eder

Method Summary

Modifier and Type	Method	Description
TableOnConditionStep<R>	and(java.lang.Boolean condition)	Deprecated. - 3.8.0 - [#4763] - Use and(Condition) (typically with DSL.trueCondition(), DSL.falseCondition(), or DSL.noCondition() as the parameter) or and(Field) instead.
TableOnConditionStep<R>	and(java.lang.String sql)	Combine the currently assembled conditions with another one using the Operator.AND operator.
TableOnConditionStep<R>	and(java.lang.String sql, java.lang.Object... bindings)	Combine the currently assembled conditions with another one using the Operator.AND operator.
TableOnConditionStep<R>	and(java.lang.String sql, QueryPart... parts)	Combine the currently assembled conditions with another one using the Operator.AND operator.
TableOnConditionStep<R>	and(Condition condition)	Combine the currently assembled conditions with another one using the Operator.AND operator.
TableOnConditionStep<R>	and(Field<java.lang.Boolean> condition)	Combine the currently assembled conditions with another one using the Operator.AND operator.
TableOnConditionStep<R>	and(SQL sql)	Combine the currently assembled conditions with another one using the Operator.AND operator.
TableOnConditionStep<R>	andExists(Select<?> select)	Combine the currently assembled conditions with an EXISTS clause using the Operator.AND operator.
TableOnConditionStep<R>	andNot(java.lang.Boolean condition)	Deprecated. - 3.8.0 - [#4763] - Use andNot(Condition) (typically with DSL.trueCondition(), DSL.falseCondition(), or DSL.noCondition() as the parameter) or andNot(Field) instead.
TableOnConditionStep<R>	andNot(Condition condition)	Combine the currently assembled conditions with a negated other one using the Operator.AND operator.
TableOnConditionStep<R>	andNot(Field<java.lang.Boolean> condition)	Combine the currently assembled conditions with a negated other one using the Operator.AND operator.
TableOnConditionStep<R>	andNotExists(Select<?> select)	Combine the currently assembled conditions with a NOT EXISTS clause using the Operator.AND operator.
TableOnConditionStep<R>	or(java.lang.Boolean condition)	Deprecated. - 3.8.0 - [#4763] - Use or(Condition) (typically with DSL.trueCondition(), DSL.falseCondition(), or DSL.noCondition() as the parameter) or or(Field) instead.
TableOnConditionStep<R>	or(java.lang.String sql)	Combine the currently assembled conditions with another one using the Operator.OR operator.
TableOnConditionStep<R>	or(java.lang.String sql, java.lang.Object... bindings)	Combine the currently assembled conditions with another one using the Operator.OR operator.
TableOnConditionStep<R>	or(java.lang.String sql, QueryPart... parts)	Combine the currently assembled conditions with another one using the Operator.OR operator.
TableOnConditionStep<R>	or(Condition condition)	Combine the currently assembled conditions with another one using the Operator.OR operator.
TableOnConditionStep<R>	or(Field<java.lang.Boolean> condition)	Combine the currently assembled conditions with another one using the Operator.OR operator.
TableOnConditionStep<R>	or(SQL sql)	Combine the currently assembled conditions with another one using the Operator.OR operator.
TableOnConditionStep<R>	orExists(Select<?> select)	Combine the currently assembled conditions with an EXISTS clause using the Operator.OR operator.
TableOnConditionStep<R>	orNot(java.lang.Boolean condition)	Deprecated. - 3.8.0 - [#4763] - Use orNot(Condition) (typically with DSL.trueCondition(), DSL.falseCondition(), or DSL.noCondition() as the parameter) or orNot(Field) instead.
TableOnConditionStep<R>	orNot(Condition condition)	Combine the currently assembled conditions with a negated other one using the Operator.OR operator.
TableOnConditionStep<R>	orNot(Field<java.lang.Boolean> condition)	Combine the currently assembled conditions with a negated other one using the Operator.OR operator.
TableOnConditionStep<R>	orNotExists(Select<?> select)	Combine the currently assembled conditions with a NOT EXISTS clause using the Operator.OR operator.

Methods inherited from interface org.jooq.Named

getName, getQualifiedName, getUnqualifiedName

Methods inherited from interface org.jooq.QueryPart

hashCode, toString

Methods inherited from interface org.jooq.Table

as, as, as, as, as, as, as, as, as, as, as, as, asOfScn, asOfScn, asOfTimestamp, asOfTimestamp, asterisk, at, at, at, crossApply, crossApply, crossApply, crossApply, crossApply, crossApply, crossJoin, crossJoin, crossJoin, crossJoin, crossJoin, crossJoin, divideBy, eq, equal, equals, forceIndex, forceIndexForGroupBy, forceIndexForJoin, forceIndexForOrderBy, from, fullJoin, fullJoin, fullJoin, fullJoin, fullJoin, fullJoin, fullOuterJoin, fullOuterJoin, fullOuterJoin, fullOuterJoin, fullOuterJoin, fullOuterJoin, getCatalog, getComment, getDataType, getIdentity, getIndexes, getKeys, getPrimaryKey, getRecordTimestamp, getRecordType, getRecordVersion, getReferences, getReferencesFrom, getReferencesTo, getSchema, ignoreIndex, ignoreIndexForGroupBy, ignoreIndexForJoin, ignoreIndexForOrderBy, innerJoin, innerJoin, innerJoin, innerJoin, innerJoin, innerJoin, join, join, join, join, join, join, join, leftAntiJoin, leftJoin, leftJoin, leftJoin, leftJoin, leftJoin, leftJoin, leftOuterJoin, leftOuterJoin, leftOuterJoin, leftOuterJoin, leftOuterJoin, leftOuterJoin, leftSemiJoin, naturalFullOuterJoin, naturalFullOuterJoin, naturalFullOuterJoin, naturalFullOuterJoin, naturalFullOuterJoin, naturalFullOuterJoin, naturalJoin, naturalJoin, naturalJoin, naturalJoin, naturalJoin, naturalJoin, naturalLeftOuterJoin, naturalLeftOuterJoin, naturalLeftOuterJoin, naturalLeftOuterJoin, naturalLeftOuterJoin, naturalLeftOuterJoin, naturalRightOuterJoin, naturalRightOuterJoin, naturalRightOuterJoin, naturalRightOuterJoin, naturalRightOuterJoin, naturalRightOuterJoin, ne, newRecord, notEqual, outerApply, outerApply, outerApply, outerApply, outerApply, outerApply, partitionBy, partitionBy, pivot, pivot, recordType, rightJoin, rightJoin, rightJoin, rightJoin, rightJoin, rightJoin, rightOuterJoin, rightOuterJoin, rightOuterJoin, rightOuterJoin, rightOuterJoin, rightOuterJoin, rowid, straightJoin, straightJoin, straightJoin, straightJoin, straightJoin, straightJoin, useIndex, useIndexForGroupBy, useIndexForJoin, useIndexForOrderBy, versionsBetweenScn, versionsBetweenScn, versionsBetweenScnMinvalue, versionsBetweenTimestamp, versionsBetweenTimestamp, versionsBetweenTimestampMinvalue, where, where, where, where, where, where, where, where, whereExists, whereNotExists, with

Methods inherited from interface org.jooq.TableLike

asTable, asTable, asTable, asTable, asTable, field, field, field, field, field, field, field, field, field, field, fields, fields, fields, fields, fields, fieldsRow, fieldStream, indexOf, indexOf, indexOf

Method Detail

and

@Support
TableOnConditionStep<R> and(Condition condition)

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

and

@Support
TableOnConditionStep<R> and(Field<java.lang.Boolean> condition)

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

and

@Deprecated
@Support
TableOnConditionStep<R> and(java.lang.Boolean condition)

Deprecated.

- 3.8.0 - [#4763] - Use and(Condition) (typically with DSL.trueCondition(), DSL.falseCondition(), or DSL.noCondition() as the parameter) or and(Field) instead. Due to ambiguity between calling this method using Field.equals(Object) argument, vs. calling the other method via a Field.equal(Object) argument, this method will be removed in the future.

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

and

@Support
@PlainSQL
TableOnConditionStep<R> and(SQL 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:

DSL.condition(SQL), SQL

and

@Support
@PlainSQL
TableOnConditionStep<R> and(java.lang.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:

DSL.condition(String), SQL

and

@Support
@PlainSQL
TableOnConditionStep<R> and(java.lang.String sql,
                            java.lang.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:

DSL.condition(String, Object...), DSL.sql(String, Object...), SQL

and

@Support
@PlainSQL
TableOnConditionStep<R> and(java.lang.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:

DSL.condition(String, QueryPart...), DSL.sql(String, QueryPart...), SQL

andNot

@Support
TableOnConditionStep<R> andNot(Condition condition)

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

andNot

@Support
TableOnConditionStep<R> andNot(Field<java.lang.Boolean> condition)

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

andNot

@Deprecated
@Support
TableOnConditionStep<R> andNot(java.lang.Boolean condition)

Deprecated.

- 3.8.0 - [#4763] - Use andNot(Condition) (typically with DSL.trueCondition(), DSL.falseCondition(), or DSL.noCondition() as the parameter) or andNot(Field) instead. Due to ambiguity between calling this method using Field.equals(Object) argument, vs. calling the other method via a Field.equal(Object) argument, this method will be removed in the future.

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

andExists

@Support
TableOnConditionStep<R> andExists(Select<?> select)

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

andNotExists

@Support
TableOnConditionStep<R> andNotExists(Select<?> select)

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

or

@Support
TableOnConditionStep<R> or(Condition condition)

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

or

@Support
TableOnConditionStep<R> or(Field<java.lang.Boolean> condition)

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

or

@Deprecated
@Support
TableOnConditionStep<R> or(java.lang.Boolean condition)

Deprecated.

- 3.8.0 - [#4763] - Use or(Condition) (typically with DSL.trueCondition(), DSL.falseCondition(), or DSL.noCondition() as the parameter) or or(Field) instead. Due to ambiguity between calling this method using Field.equals(Object) argument, vs. calling the other method via a Field.equal(Object) argument, this method will be removed in the future.

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

or

@Support
@PlainSQL
TableOnConditionStep<R> or(SQL 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:

DSL.condition(SQL), SQL

or

@Support
@PlainSQL
TableOnConditionStep<R> or(java.lang.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:

DSL.condition(String), SQL

or

@Support
@PlainSQL
TableOnConditionStep<R> or(java.lang.String sql,
                           java.lang.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:

DSL.condition(String, Object...), DSL.sql(String, Object...), SQL

or

@Support
@PlainSQL
TableOnConditionStep<R> or(java.lang.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:

DSL.condition(String, QueryPart...), DSL.sql(String, QueryPart...), SQL

orNot

@Support
TableOnConditionStep<R> orNot(Condition condition)

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

orNot

@Support
TableOnConditionStep<R> orNot(Field<java.lang.Boolean> condition)

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

orNot

@Deprecated
@Support
TableOnConditionStep<R> orNot(java.lang.Boolean condition)

Deprecated.

- 3.8.0 - [#4763] - Use orNot(Condition) (typically with DSL.trueCondition(), DSL.falseCondition(), or DSL.noCondition() as the parameter) or orNot(Field) instead. Due to ambiguity between calling this method using Field.equals(Object) argument, vs. calling the other method via a Field.equal(Object) argument, this method will be removed in the future.

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

orExists

@Support
TableOnConditionStep<R> orExists(Select<?> select)

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

orNotExists

@Support
TableOnConditionStep<R> orNotExists(Select<?> select)

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