Uses of Interface
org.jooq.MergeOnConditionStep

Packages that use MergeOnConditionStep

Package	Description
org.jooq	The org.jooq package contains jOOQ's public API.

Uses of MergeOnConditionStep in org.jooq

Methods in org.jooq that return MergeOnConditionStep

Modifier and Type	Method and Description
MergeOnConditionStep<R>	MergeOnConditionStep.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.
MergeOnConditionStep<R>	MergeOnConditionStep.and(Condition condition) Combine the currently assembled conditions with another one using the Operator.AND operator and proceed to the next step.
MergeOnConditionStep<R>	MergeOnConditionStep.and(Field<Boolean> condition) Combine the currently assembled conditions with another one using the Operator.AND operator and proceed to the next step.
MergeOnConditionStep<R>	MergeOnConditionStep.and(SQL sql) Combine the currently assembled conditions with another one using the Operator.AND operator and proceed to the next step.
MergeOnConditionStep<R>	MergeOnConditionStep.and(String sql) Combine the currently assembled conditions with another one using the Operator.AND operator and proceed to the next step.
MergeOnConditionStep<R>	MergeOnConditionStep.and(String sql, Object... bindings) Combine the currently assembled conditions with another one using the Operator.AND operator and proceed to the next step.
MergeOnConditionStep<R>	MergeOnConditionStep.and(String sql, QueryPart... parts) Combine the currently assembled conditions with another one using the Operator.AND operator and proceed to the next step.
MergeOnConditionStep<R>	MergeOnConditionStep.andExists(Select<?> select) Combine the currently assembled conditions with an EXISTS clause using the Operator.AND operator and proceed to the next step.
MergeOnConditionStep<R>	MergeOnConditionStep.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.
MergeOnConditionStep<R>	MergeOnConditionStep.andNot(Condition condition) Combine the currently assembled conditions with a negated other one using the Operator.AND operator and proceed to the next step.
MergeOnConditionStep<R>	MergeOnConditionStep.andNot(Field<Boolean> condition) Combine the currently assembled conditions with a negated other one using the Operator.AND operator and proceed to the next step.
MergeOnConditionStep<R>	MergeOnConditionStep.andNotExists(Select<?> select) Combine the currently assembled conditions with a NOT EXISTS clause using the Operator.AND operator and proceed to the next step.
MergeOnConditionStep<R>	MergeOnStep.on(Boolean condition) Deprecated. - 3.8.0 - [#4763] - Use MergeOnStep.on(Condition...) or MergeOnStep.on(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.
MergeOnConditionStep<R>	MergeOnStep.on(Condition... conditions) Provide join conditions and proceed to the next step, connecting them with each other with Operator.AND.
MergeOnConditionStep<R>	MergeOnStep.on(Field<Boolean> condition) Provide join conditions and proceed to the next step
MergeOnConditionStep<R>	MergeOnStep.on(SQL sql) Provide join conditions and proceed to the next step NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity.
MergeOnConditionStep<R>	MergeOnStep.on(String sql) Provide join conditions and proceed to the next step NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity.
MergeOnConditionStep<R>	MergeOnStep.on(String sql, Object... bindings) Provide join conditions and proceed to the next step NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity.
MergeOnConditionStep<R>	MergeOnStep.on(String sql, QueryPart... parts) Provide join conditions and proceed to the next step NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity.
MergeOnConditionStep<R>	MergeOnConditionStep.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.
MergeOnConditionStep<R>	MergeOnConditionStep.or(Condition condition) Combine the currently assembled conditions with another one using the Operator.OR operator and proceed to the next step.
MergeOnConditionStep<R>	MergeOnConditionStep.or(Field<Boolean> condition) Combine the currently assembled conditions with another one using the Operator.OR operator and proceed to the next step.
MergeOnConditionStep<R>	MergeOnConditionStep.or(SQL sql) Combine the currently assembled conditions with another one using the Operator.OR operator and proceed to the next step.
MergeOnConditionStep<R>	MergeOnConditionStep.or(String sql) Combine the currently assembled conditions with another one using the Operator.OR operator and proceed to the next step.
MergeOnConditionStep<R>	MergeOnConditionStep.or(String sql, Object... bindings) Combine the currently assembled conditions with another one using the Operator.OR operator and proceed to the next step.
MergeOnConditionStep<R>	MergeOnConditionStep.or(String sql, QueryPart... parts) Combine the currently assembled conditions with another one using the Operator.OR operator and proceed to the next step.
MergeOnConditionStep<R>	MergeOnConditionStep.orExists(Select<?> select) Combine the currently assembled conditions with an EXISTS clause using the Operator.OR operator and proceed to the next step.
MergeOnConditionStep<R>	MergeOnConditionStep.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.
MergeOnConditionStep<R>	MergeOnConditionStep.orNot(Condition condition) Combine the currently assembled conditions with a negated other one using the Operator.OR operator and proceed to the next step.
MergeOnConditionStep<R>	MergeOnConditionStep.orNot(Field<Boolean> condition) Combine the currently assembled conditions with a negated other one using the Operator.OR operator and proceed to the next step.
MergeOnConditionStep<R>	MergeOnConditionStep.orNotExists(Select<?> select) Combine the currently assembled conditions with a NOT EXISTS clause using the Operator.OR operator and proceed to the next step.