org.jooq

Interface SelectHavingConditionStep<R extends Record>

All Superinterfaces:

Attachable, AutoCloseable, FieldLike, Iterable<R>, org.reactivestreams.Publisher<R>, Query, QueryPart, ResultQuery<R>, Select<R>, SelectCorrelatedSubqueryStep<R>, SelectFinalStep<R>, SelectForStep<R>, SelectForUpdateStep<R>, SelectLimitStep<R>, SelectOptionStep<R>, SelectOrderByStep<R>, SelectQualifyStep<R>, SelectUnionStep<R>, SelectWindowStep<R>, Serializable, Statement, TableLike<R>

public interface SelectHavingConditionStep<R extends Record>
extends SelectWindowStep<R>

This type is used for the Select's DSL API when selecting generic Record types.

Example:

 -- get all authors' first and last names, and the number
 -- of books they've written in German, if they have written
 -- more than five books in German in the last three years
 -- (from 2011), and sort those authors by last names
 -- limiting results to the second and third row

   SELECT T_AUTHOR.FIRST_NAME, T_AUTHOR.LAST_NAME, COUNT(*)
     FROM T_AUTHOR
     JOIN T_BOOK ON T_AUTHOR.ID = T_BOOK.AUTHOR_ID
    WHERE T_BOOK.LANGUAGE = 'DE'
      AND T_BOOK.PUBLISHED > '2008-01-01'
 GROUP BY T_AUTHOR.FIRST_NAME, T_AUTHOR.LAST_NAME
   HAVING COUNT(*) > 5
 ORDER BY T_AUTHOR.LAST_NAME ASC NULLS FIRST
    LIMIT 2
   OFFSET 1
      FOR UPDATE
       OF FIRST_NAME, LAST_NAME
       NO WAIT
 

Its equivalent in jOOQ

 create.select(TAuthor.FIRST_NAME, TAuthor.LAST_NAME, create.count())
       .from(T_AUTHOR)
       .join(T_BOOK).on(TBook.AUTHOR_ID.equal(TAuthor.ID))
       .where(TBook.LANGUAGE.equal("DE"))
       .and(TBook.PUBLISHED.greaterThan(parseDate('2008-01-01')))
       .groupBy(TAuthor.FIRST_NAME, TAuthor.LAST_NAME)
       .having(create.count().greaterThan(5))
       .orderBy(TAuthor.LAST_NAME.asc().nullsFirst())
       .limit(2)
       .offset(1)
       .forUpdate()
       .of(TAuthor.FIRST_NAME, TAuthor.LAST_NAME)
       .noWait();
 

Refer to the manual for more details

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 and Description
@NotNull SelectHavingConditionStep<R>	and(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.
@NotNull SelectHavingConditionStep<R>	and(Condition condition) Combine the currently assembled conditions with another one using the Operator.AND operator and proceed to the next step.
@NotNull SelectHavingConditionStep<R>	and(Field<Boolean> condition) Combine the currently assembled conditions with another one using the Operator.AND operator and proceed to the next step.
@NotNull SelectHavingConditionStep<R>	and(SQL sql) Combine the currently assembled conditions with another one using the Operator.AND operator and proceed to the next step.
@NotNull SelectHavingConditionStep<R>	and(String sql) Combine the currently assembled conditions with another one using the Operator.AND operator and proceed to the next step.
@NotNull SelectHavingConditionStep<R>	and(String sql, Object... bindings) Combine the currently assembled conditions with another one using the Operator.AND operator and proceed to the next step.
@NotNull SelectHavingConditionStep<R>	and(String sql, QueryPart... parts) Combine the currently assembled conditions with another one using the Operator.AND operator and proceed to the next step.
@NotNull SelectHavingConditionStep<R>	andExists(Select<?> select) Combine the currently assembled conditions with an EXISTS clause using the Operator.AND operator and proceed to the next step.
@NotNull SelectHavingConditionStep<R>	andNot(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.
@NotNull SelectHavingConditionStep<R>	andNot(Condition condition) Combine the currently assembled conditions with a negated other one using the Operator.AND operator and proceed to the next step.
@NotNull SelectHavingConditionStep<R>	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.
@NotNull SelectHavingConditionStep<R>	andNotExists(Select<?> select) Combine the currently assembled conditions with a NOT EXISTS clause using the Operator.AND operator and proceed to the next step.
@NotNull SelectHavingConditionStep<R>	or(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.
@NotNull SelectHavingConditionStep<R>	or(Condition condition) Combine the currently assembled conditions with another one using the Operator.OR operator and proceed to the next step.
@NotNull SelectHavingConditionStep<R>	or(Field<Boolean> condition) Combine the currently assembled conditions with another one using the Operator.OR operator and proceed to the next step.
@NotNull SelectHavingConditionStep<R>	or(SQL sql) Combine the currently assembled conditions with another one using the Operator.OR operator and proceed to the next step.
@NotNull SelectHavingConditionStep<R>	or(String sql) Combine the currently assembled conditions with another one using the Operator.OR operator and proceed to the next step.
@NotNull SelectHavingConditionStep<R>	or(String sql, Object... bindings) Combine the currently assembled conditions with another one using the Operator.OR operator and proceed to the next step.
@NotNull SelectHavingConditionStep<R>	or(String sql, QueryPart... parts) Combine the currently assembled conditions with another one using the Operator.OR operator and proceed to the next step.
@NotNull SelectHavingConditionStep<R>	orExists(Select<?> select) Combine the currently assembled conditions with an EXISTS clause using the Operator.OR operator and proceed to the next step.
@NotNull SelectHavingConditionStep<R>	orNot(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.
@NotNull SelectHavingConditionStep<R>	orNot(Condition condition) Combine the currently assembled conditions with a negated other one using the Operator.OR operator and proceed to the next step.
@NotNull SelectHavingConditionStep<R>	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.
@NotNull SelectHavingConditionStep<R>	orNotExists(Select<?> select) Combine the currently assembled conditions with a NOT EXISTS clause using the Operator.OR operator and proceed to the next step.

Methods inherited from interface org.jooq.SelectWindowStep

window, window

Methods inherited from interface org.jooq.SelectQualifyStep

qualify, qualify, qualify, qualify, qualify, qualify, qualify, qualify

Methods inherited from interface org.jooq.SelectOrderByStep

orderBy, orderBy, orderBy, orderBy, orderBy, orderBy, orderBy, orderBy, orderBy, orderBy, orderBy, orderBy, orderBy, orderBy, orderBy, orderBy, orderBy, orderBy, orderBy, orderBy, orderBy, orderBy, orderBy, orderBy, orderBy

Methods inherited from interface org.jooq.SelectLimitStep

limit, limit, limit, limit, limit, limit, limit, limit, limit, limit, offset, offset, offset

Methods inherited from interface org.jooq.SelectForUpdateStep

forKeyShare, forNoKeyUpdate, forShare, forUpdate

Methods inherited from interface org.jooq.SelectOptionStep

option

Methods inherited from interface org.jooq.SelectUnionStep

except, exceptAll, intersect, intersectAll, union, unionAll

Methods inherited from interface org.jooq.SelectCorrelatedSubqueryStep

between, between, between, between, betweenSymmetric, betweenSymmetric, betweenSymmetric, betweenSymmetric, compare, compare, compare, eq, eq, eq, equal, equal, equal, ge, ge, ge, greaterOrEqual, greaterOrEqual, greaterOrEqual, greaterThan, greaterThan, greaterThan, gt, gt, gt, in, in, isDistinctFrom, isDistinctFrom, isDistinctFrom, isNotDistinctFrom, isNotDistinctFrom, isNotDistinctFrom, isNotNull, isNull, le, le, le, lessOrEqual, lessOrEqual, lessOrEqual, lessThan, lessThan, lessThan, lt, lt, lt, ne, ne, ne, notBetween, notBetween, notBetween, notBetween, notBetweenSymmetric, notBetweenSymmetric, notBetweenSymmetric, notBetweenSymmetric, notEqual, notEqual, notEqual, notIn, notIn

Methods inherited from interface org.jooq.SelectFinalStep

getQuery

Methods inherited from interface org.jooq.Select

fetchCount, getSelect

Methods inherited from interface org.jooq.ResultQuery

bind, bind, coerce, coerce, coerce, coerce, coerce, coerce, coerce, coerce, coerce, coerce, coerce, coerce, coerce, coerce, coerce, coerce, coerce, coerce, coerce, coerce, coerce, coerce, coerce, coerce, coerce, collect, fetch, fetch, fetch, fetch, fetch, fetch, fetch, fetch, fetch, fetch, fetch, fetch, fetch, fetch, fetchAny, fetchAny, fetchAny, fetchAny, fetchAny, fetchAny, fetchAny, fetchAny, fetchAny, fetchAny, fetchAny, fetchAny, fetchAny, fetchAny, fetchAnyArray, fetchAnyInto, fetchAnyInto, fetchAnyMap, fetchArray, fetchArray, fetchArray, fetchArray, fetchArray, fetchArray, fetchArray, fetchArray, fetchArray, fetchArray, fetchArray, fetchArray, fetchArray, fetchArrays, fetchAsync, fetchAsync, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchInto, fetchInto, fetchInto, fetchLater, fetchLater, fetchLazy, fetchLazy, fetchMany, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMaps, fetchOne, fetchOne, fetchOne, fetchOne, fetchOne, fetchOne, fetchOne, fetchOne, fetchOne, fetchOne, fetchOne, fetchOne, fetchOne, fetchOne, fetchOneArray, fetchOneInto, fetchOneInto, fetchOneMap, fetchOptional, fetchOptional, fetchOptional, fetchOptional, fetchOptional, fetchOptional, fetchOptional, fetchOptional, fetchOptional, fetchOptional, fetchOptional, fetchOptional, fetchOptional, fetchOptional, fetchOptionalArray, fetchOptionalInto, fetchOptionalInto, fetchOptionalMap, fetchResultSet, fetchSet, fetchSet, fetchSet, fetchSet, fetchSet, fetchSet, fetchSet, fetchSet, fetchSet, fetchSet, fetchSet, fetchSet, fetchSet, fetchSingle, fetchSingle, fetchSingle, fetchSingle, fetchSingle, fetchSingle, fetchSingle, fetchSingle, fetchSingle, fetchSingle, fetchSingle, fetchSingle, fetchSingle, fetchSingle, fetchSingleArray, fetchSingleInto, fetchSingleInto, fetchSingleMap, fetchSize, fetchStream, fetchStreamInto, fetchStreamInto, forEach, getRecordType, getResult, intern, intern, intern, intern, iterator, keepStatement, maxRows, poolable, queryTimeout, resultSetConcurrency, resultSetHoldability, resultSetType, spliterator, stream

Methods inherited from interface org.jooq.Query

cancel, close, execute, executeAsync, executeAsync, getBindValues, getParam, getParams, getSQL, getSQL, getSQL, isExecutable

Methods inherited from interface org.jooq.QueryPart

equals, hashCode, toString

Methods inherited from interface org.jooq.Attachable

attach, configuration, detach

Methods inherited from interface org.reactivestreams.Publisher

subscribe

Methods inherited from interface org.jooq.TableLike

asTable, asTable, asTable, asTable, 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

Methods inherited from interface org.jooq.FieldLike

asField, asField, asField

Method Detail

and

@NotNull
 @Support
@NotNull SelectHavingConditionStep<R> and(Condition condition)

Combine the currently assembled conditions with another one using the Operator.AND operator and proceed to the next step.

and

@NotNull
 @Support
@NotNull SelectHavingConditionStep<R> and(Field<Boolean> condition)

Combine the currently assembled conditions with another one using the Operator.AND operator and proceed to the next step.

and

@Deprecated
 @NotNull
 @Support
@NotNull SelectHavingConditionStep<R> and(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 proceed to the next step.

and

@NotNull
 @Support
 @PlainSQL
@NotNull SelectHavingConditionStep<R> and(SQL sql)

Combine the currently assembled conditions with another one using the Operator.AND operator and proceed to the next step.

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

@NotNull
 @Support
 @PlainSQL
@NotNull SelectHavingConditionStep<R> and(String sql)

Combine the currently assembled conditions with another one using the Operator.AND operator and proceed to the next step.

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

@NotNull
 @Support
 @PlainSQL
@NotNull SelectHavingConditionStep<R> and(String sql,
                                                                           Object... bindings)

Combine the currently assembled conditions with another one using the Operator.AND operator and proceed to the next step.

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

@NotNull
 @Support
 @PlainSQL
@NotNull SelectHavingConditionStep<R> and(String sql,
                                                                           QueryPart... parts)

Combine the currently assembled conditions with another one using the Operator.AND operator and proceed to the next step.

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

@NotNull
 @Support
@NotNull SelectHavingConditionStep<R> andNot(Condition condition)

Combine the currently assembled conditions with a negated other one using the Operator.AND operator and proceed to the next step.

andNot

@NotNull
 @Support
@NotNull SelectHavingConditionStep<R> 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.

andNot

@Deprecated
 @NotNull
 @Support
@NotNull SelectHavingConditionStep<R> andNot(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 and proceed to the next step.

andExists

@NotNull
 @Support
@NotNull SelectHavingConditionStep<R> andExists(Select<?> select)

Combine the currently assembled conditions with an EXISTS clause using the Operator.AND operator and proceed to the next step.

andNotExists

@NotNull
 @Support
@NotNull SelectHavingConditionStep<R> andNotExists(Select<?> select)

Combine the currently assembled conditions with a NOT EXISTS clause using the Operator.AND operator and proceed to the next step.

or

@NotNull
 @Support
@NotNull SelectHavingConditionStep<R> or(Condition condition)

Combine the currently assembled conditions with another one using the Operator.OR operator and proceed to the next step.

or

@NotNull
 @Support
@NotNull SelectHavingConditionStep<R> or(Field<Boolean> condition)

Combine the currently assembled conditions with another one using the Operator.OR operator and proceed to the next step.

or

@Deprecated
 @NotNull
 @Support
@NotNull SelectHavingConditionStep<R> or(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 and proceed to the next step.

or

@NotNull
 @Support
 @PlainSQL
@NotNull SelectHavingConditionStep<R> or(SQL sql)

Combine the currently assembled conditions with another one using the Operator.OR operator and proceed to the next step.

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

@NotNull
 @Support
 @PlainSQL
@NotNull SelectHavingConditionStep<R> or(String sql)

Combine the currently assembled conditions with another one using the Operator.OR operator and proceed to the next step.

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

@NotNull
 @Support
 @PlainSQL
@NotNull SelectHavingConditionStep<R> or(String sql,
                                                                          Object... bindings)

Combine the currently assembled conditions with another one using the Operator.OR operator and proceed to the next step.

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

@NotNull
 @Support
 @PlainSQL
@NotNull SelectHavingConditionStep<R> or(String sql,
                                                                          QueryPart... parts)

Combine the currently assembled conditions with another one using the Operator.OR operator and proceed to the next step.

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

@NotNull
 @Support
@NotNull SelectHavingConditionStep<R> orNot(Condition condition)

Combine the currently assembled conditions with a negated other one using the Operator.OR operator and proceed to the next step.

orNot

@NotNull
 @Support
@NotNull SelectHavingConditionStep<R> 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.

orNot

@Deprecated
 @NotNull
 @Support
@NotNull SelectHavingConditionStep<R> orNot(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 and proceed to the next step.

orExists

@NotNull
 @Support
@NotNull SelectHavingConditionStep<R> orExists(Select<?> select)

Combine the currently assembled conditions with an EXISTS clause using the Operator.OR operator and proceed to the next step.

orNotExists

@NotNull
 @Support
@NotNull SelectHavingConditionStep<R> orNotExists(Select<?> select)

Combine the currently assembled conditions with a NOT EXISTS clause using the Operator.OR operator and proceed to the next step.