DivideByOnConditionStep (jOOQ 3.9.6 API)

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

All Methods Instance Methods Abstract Methods Deprecated Methods
Modifier and Type	Method and Description
`DivideByOnConditionStep`	`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.
`DivideByOnConditionStep`	`and(Condition condition)` Combine the currently assembled conditions with another one using the `Operator.AND` operator.
`DivideByOnConditionStep`	`and(Field<Boolean> condition)` Combine the currently assembled conditions with another one using the `Operator.AND` operator.
`DivideByOnConditionStep`	`and(SQL sql)` 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(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.
`DivideByOnConditionStep`	`andNot(Condition condition)` Combine the currently assembled conditions with a negated other one using the `Operator.AND` operator.
`DivideByOnConditionStep`	`andNot(Field<Boolean> 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(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.
`DivideByOnConditionStep`	`or(Condition condition)` Combine the currently assembled conditions with another one using the `Operator.OR` operator.
`DivideByOnConditionStep`	`or(Field<Boolean> condition)` Combine the currently assembled conditions with another one using the `Operator.OR` operator.
`DivideByOnConditionStep`	`or(SQL sql)` 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(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.
`DivideByOnConditionStep`	`orNot(Condition condition)` Combine the currently assembled conditions with a negated other one using the `Operator.OR` operator.
`DivideByOnConditionStep`	`orNot(Field<Boolean> 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(Field<Boolean> condition)
```
    Combine the currently assembled conditions with another one using the Operator.AND operator.
  - and
```
@Deprecated
 @Support
DivideByOnConditionStep 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.
    
    Combine the currently assembled conditions with another one using the Operator.AND operator.
  - and
```
@Support
 @PlainSQL
DivideByOnConditionStep 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
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:
    
    DSL.condition(String), SQL
  - and
```
@Support
 @PlainSQL
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:
    
    DSL.condition(String, Object...), DSL.sql(String, Object...), SQL
  - and
```
@Support
 @PlainSQL
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:
    
    DSL.condition(String, QueryPart...), DSL.sql(String, QueryPart...), SQL
  - andNot
```
@Support
DivideByOnConditionStep andNot(Condition condition)
```
    Combine the currently assembled conditions with a negated other one using the Operator.AND operator.
  - andNot
```
@Support
DivideByOnConditionStep andNot(Field<Boolean> condition)
```
    Combine the currently assembled conditions with a negated other one using the Operator.AND operator.
  - andNot
```
@Deprecated
 @Support
DivideByOnConditionStep 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.
    
    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(Field<Boolean> condition)
```
    Combine the currently assembled conditions with another one using the Operator.OR operator.
  - or
```
@Deprecated
 @Support
DivideByOnConditionStep 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.
    
    Combine the currently assembled conditions with another one using the Operator.OR operator.
  - or
```
@Support
 @PlainSQL
DivideByOnConditionStep 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
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:
    
    DSL.condition(String), SQL
  - or
```
@Support
 @PlainSQL
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:
    
    DSL.condition(String, Object...), DSL.sql(String, Object...), SQL
  - or
```
@Support
 @PlainSQL
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:
    
    DSL.condition(String, QueryPart...), DSL.sql(String, QueryPart...), SQL
  - orNot
```
@Support
DivideByOnConditionStep orNot(Condition condition)
```
    Combine the currently assembled conditions with a negated other one using the Operator.OR operator.
  - orNot
```
@Support
DivideByOnConditionStep orNot(Field<Boolean> condition)
```
    Combine the currently assembled conditions with a negated other one using the Operator.OR operator.
  - orNot
```
@Deprecated
 @Support
DivideByOnConditionStep 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.
    
    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.

Interface DivideByOnConditionStep

Method Summary

Methods inherited from interface org.jooq.DivideByReturningStep

Method Detail

and

and

and

and

and

and

and

andNot

andNot

andNot

andExists

andNotExists

or

or

or

or

or

or

or

orNot

orNot

orNot

orExists

orNotExists