Module org.jooq

Package org.jooq

Interface DivideByOnStep

public interface DivideByOnStep

An intermediate type for the construction of a relational division

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
@NotNull DivideByOnConditionStep	on(String sql)	Add a division condition to the DIVIDE BY clause
@NotNull DivideByOnConditionStep	on(String sql, Object... bindings)	Add a division condition to the DIVIDE BY clause
@NotNull DivideByOnConditionStep	on(String sql, QueryPart... parts)	Add a division condition to the DIVIDE BY clause
@NotNull DivideByOnConditionStep	on(Condition condition)	Add a division condition to the DIVIDE BY clause, connecting them with each other with Operator.AND.
@NotNull DivideByOnConditionStep	on(Condition... conditions)	Add a division condition to the DIVIDE BY clause, connecting them with each other with Operator.AND.
@NotNull DivideByOnConditionStep	on(Field<Boolean> condition)	Add a division condition to the DIVIDE BY clause
@NotNull DivideByOnConditionStep	on(SQL sql)	Add a division condition to the DIVIDE BY clause

Method Details

on

@NotNull
@Support({ACCESS,ASE,AURORA_MYSQL,AURORA_POSTGRES,CLICKHOUSE,COCKROACHDB,CUBRID,DB2,DERBY,DUCKDB,EXASOL,FIREBIRD,H2,HANA,HSQLDB,INFORMIX,INGRES,MARIADB,MYSQL,ORACLE,POSTGRES,REDSHIFT,SQLDATAWAREHOUSE,SQLITE,SQLSERVER,SYBASE,TERADATA,VERTICA})
@NotNull DivideByOnConditionStep on(Condition condition)

Add a division condition to the DIVIDE BY clause, connecting them with each other with Operator.AND.

on

@NotNull
@Support({ACCESS,ASE,AURORA_MYSQL,AURORA_POSTGRES,CLICKHOUSE,COCKROACHDB,CUBRID,DB2,DERBY,DUCKDB,EXASOL,FIREBIRD,H2,HANA,HSQLDB,INFORMIX,INGRES,MARIADB,MYSQL,ORACLE,POSTGRES,REDSHIFT,SQLDATAWAREHOUSE,SQLITE,SQLSERVER,SYBASE,TERADATA,VERTICA})
@NotNull DivideByOnConditionStep on(Condition... conditions)

Add a division condition to the DIVIDE BY clause, connecting them with each other with Operator.AND.

on

@NotNull
@Support({ACCESS,ASE,AURORA_MYSQL,AURORA_POSTGRES,CLICKHOUSE,COCKROACHDB,CUBRID,DB2,DERBY,DUCKDB,EXASOL,FIREBIRD,H2,HANA,HSQLDB,INFORMIX,INGRES,MARIADB,MYSQL,ORACLE,POSTGRES,REDSHIFT,SQLDATAWAREHOUSE,SQLITE,SQLSERVER,SYBASE,TERADATA,VERTICA})
@NotNull DivideByOnConditionStep on(Field<Boolean> condition)

Add a division condition to the DIVIDE BY clause

on

@NotNull
@Support({ACCESS,ASE,AURORA_MYSQL,AURORA_POSTGRES,CLICKHOUSE,COCKROACHDB,CUBRID,DB2,DERBY,DUCKDB,EXASOL,FIREBIRD,H2,HANA,HSQLDB,INFORMIX,INGRES,MARIADB,MYSQL,ORACLE,POSTGRES,REDSHIFT,SQLDATAWAREHOUSE,SQLITE,SQLSERVER,SYBASE,TERADATA,VERTICA})
@PlainSQL
@NotNull DivideByOnConditionStep on(SQL sql)

Add a division condition to the DIVIDE BY clause

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

on

@NotNull
@Support({ACCESS,ASE,AURORA_MYSQL,AURORA_POSTGRES,CLICKHOUSE,COCKROACHDB,CUBRID,DB2,DERBY,DUCKDB,EXASOL,FIREBIRD,H2,HANA,HSQLDB,INFORMIX,INGRES,MARIADB,MYSQL,ORACLE,POSTGRES,REDSHIFT,SQLDATAWAREHOUSE,SQLITE,SQLSERVER,SYBASE,TERADATA,VERTICA})
@PlainSQL
@NotNull DivideByOnConditionStep on(String sql)

Add a division condition to the DIVIDE BY clause

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

on

@NotNull
@Support({ACCESS,ASE,AURORA_MYSQL,AURORA_POSTGRES,CLICKHOUSE,COCKROACHDB,CUBRID,DB2,DERBY,DUCKDB,EXASOL,FIREBIRD,H2,HANA,HSQLDB,INFORMIX,INGRES,MARIADB,MYSQL,ORACLE,POSTGRES,REDSHIFT,SQLDATAWAREHOUSE,SQLITE,SQLSERVER,SYBASE,TERADATA,VERTICA})
@PlainSQL
@NotNull DivideByOnConditionStep on(String sql,
 Object... bindings)

Add a division condition to the DIVIDE BY clause

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

on

@NotNull
@Support({ACCESS,ASE,AURORA_MYSQL,AURORA_POSTGRES,CLICKHOUSE,COCKROACHDB,CUBRID,DB2,DERBY,DUCKDB,EXASOL,FIREBIRD,H2,HANA,HSQLDB,INFORMIX,INGRES,MARIADB,MYSQL,ORACLE,POSTGRES,REDSHIFT,SQLDATAWAREHOUSE,SQLITE,SQLSERVER,SYBASE,TERADATA,VERTICA})
@PlainSQL
@NotNull DivideByOnConditionStep on(String sql,
 QueryPart... parts)

Add a division condition to the DIVIDE BY clause

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