public interface TableOnConditionStep<R extends Record> extends Table<R>
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.Modifier and Type | Method and Description |
---|---|
TableOnConditionStep<R> |
and(Boolean condition)
Deprecated.
- 3.8.0 - [#4763] - Use
and(Condition) 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. |
TableOnConditionStep<R> |
and(Condition condition)
Combine the currently assembled conditions with another one using the
Operator.AND operator. |
TableOnConditionStep<R> |
and(Field<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> |
and(String sql)
Combine the currently assembled conditions with another one using the
Operator.AND operator. |
TableOnConditionStep<R> |
and(String sql,
Object... bindings)
Combine the currently assembled conditions with another one using the
Operator.AND operator. |
TableOnConditionStep<R> |
and(String sql,
QueryPart... parts)
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(Boolean condition)
Deprecated.
- 3.8.0 - [#4763] - Use
andNot(Condition) 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. |
TableOnConditionStep<R> |
andNot(Condition condition)
Combine the currently assembled conditions with a negated other one using
the
Operator.AND operator. |
TableOnConditionStep<R> |
andNot(Field<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(Boolean condition)
Deprecated.
- 3.8.0 - [#4763] - Use
or(Condition) 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. |
TableOnConditionStep<R> |
or(Condition condition)
Combine the currently assembled conditions with another one using the
Operator.OR operator. |
TableOnConditionStep<R> |
or(Field<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> |
or(String sql)
Combine the currently assembled conditions with another one using the
Operator.OR operator. |
TableOnConditionStep<R> |
or(String sql,
Object... bindings)
Combine the currently assembled conditions with another one using the
Operator.OR operator. |
TableOnConditionStep<R> |
or(String sql,
QueryPart... parts)
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(Boolean condition)
Deprecated.
- 3.8.0 - [#4763] - Use
orNot(Condition) 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. |
TableOnConditionStep<R> |
orNot(Condition condition)
Combine the currently assembled conditions with a negated other one using
the
Operator.OR operator. |
TableOnConditionStep<R> |
orNot(Field<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. |
as, as, asOfScn, asOfScn, asOfTimestamp, asOfTimestamp, at, at, at, crossApply, crossApply, crossApply, crossApply, crossApply, crossApply, crossJoin, crossJoin, crossJoin, crossJoin, crossJoin, crossJoin, divideBy, eq, equal, equals, forceIndex, forceIndexForGroupBy, forceIndexForJoin, forceIndexForOrderBy, fullOuterJoin, fullOuterJoin, fullOuterJoin, fullOuterJoin, fullOuterJoin, fullOuterJoin, getComment, getDataType, getIdentity, getKeys, getName, 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, 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, pivot, pivot, recordType, rightJoin, rightJoin, rightJoin, rightJoin, rightJoin, rightJoin, rightOuterJoin, rightOuterJoin, rightOuterJoin, rightOuterJoin, rightOuterJoin, rightOuterJoin, straightJoin, straightJoin, straightJoin, straightJoin, straightJoin, straightJoin, useIndex, useIndexForGroupBy, useIndexForJoin, useIndexForOrderBy, versionsBetweenScn, versionsBetweenScn, versionsBetweenScnMinvalue, versionsBetweenTimestamp, versionsBetweenTimestamp, versionsBetweenTimestampMinvalue, with
@Support TableOnConditionStep<R> and(Condition condition)
Operator.AND
operator.@Support TableOnConditionStep<R> and(Field<Boolean> condition)
Operator.AND
operator.@Deprecated @Support TableOnConditionStep<R> and(Boolean condition)
and(Condition)
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.Operator.AND
operator.@Support @PlainSQL TableOnConditionStep<R> and(SQL sql)
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!
DSL.condition(SQL)
,
SQL
@Support @PlainSQL TableOnConditionStep<R> and(String sql)
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!
DSL.condition(String)
,
SQL
@Support @PlainSQL TableOnConditionStep<R> and(String sql, Object... bindings)
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!
DSL.condition(String, Object...)
,
SQL
@Support @PlainSQL TableOnConditionStep<R> and(String sql, QueryPart... parts)
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!
DSL.condition(String, QueryPart...)
,
SQL
@Support TableOnConditionStep<R> andNot(Condition condition)
Operator.AND
operator.@Support TableOnConditionStep<R> andNot(Field<Boolean> condition)
Operator.AND
operator.@Deprecated @Support TableOnConditionStep<R> andNot(Boolean condition)
andNot(Condition)
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.Operator.AND
operator.@Support TableOnConditionStep<R> andExists(Select<?> select)
EXISTS
clause using the Operator.AND
operator.@Support TableOnConditionStep<R> andNotExists(Select<?> select)
NOT EXISTS
clause using the Operator.AND
operator.@Support TableOnConditionStep<R> or(Condition condition)
Operator.OR
operator.@Support TableOnConditionStep<R> or(Field<Boolean> condition)
Operator.OR
operator.@Deprecated @Support TableOnConditionStep<R> or(Boolean condition)
or(Condition)
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.Operator.OR
operator.@Support @PlainSQL TableOnConditionStep<R> or(SQL sql)
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!
DSL.condition(SQL)
,
SQL
@Support @PlainSQL TableOnConditionStep<R> or(String sql)
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!
DSL.condition(String)
,
SQL
@Support @PlainSQL TableOnConditionStep<R> or(String sql, Object... bindings)
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!
DSL.condition(String, Object...)
,
SQL
@Support @PlainSQL TableOnConditionStep<R> or(String sql, QueryPart... parts)
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!
DSL.condition(String, QueryPart...)
,
SQL
@Support TableOnConditionStep<R> orNot(Condition condition)
Operator.OR
operator.@Support TableOnConditionStep<R> orNot(Field<Boolean> condition)
Operator.OR
operator.@Deprecated @Support TableOnConditionStep<R> orNot(Boolean condition)
orNot(Condition)
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.Operator.OR
operator.@Support TableOnConditionStep<R> orExists(Select<?> select)
EXISTS
clause using the Operator.OR
operator.@Support TableOnConditionStep<R> orNotExists(Select<?> select)
NOT EXISTS
clause using the Operator.OR
operator.Copyright © 2016. All Rights Reserved.