Package org.jooq

Interface DeleteOrderByStep<R extends Record>

  • All Superinterfaces:
    Attachable, java.lang.AutoCloseable, Delete<R>, DeleteFinalStep<R>, DeleteLimitStep<R>, DeleteReturningStep<R>, java.util.concurrent.Flow.Publisher<java.lang.Integer>, org.reactivestreams.Publisher<java.lang.Integer>, Query, QueryPart, RowCountQuery,, Statement
    All Known Subinterfaces:
    DeleteConditionStep<R>, DeleteWhereStep<R>

    public interface DeleteOrderByStep<R extends Record>
    extends DeleteLimitStep<R>
    This type is used for the Delete's DSL API.


     DSLContext create = DSL.using(configuration);

    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:

    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
    Lukas Eder
    • Method Detail

      • orderBy

        DeleteLimitStep<R> orderBy​(int... fieldIndexes)
        Add an ORDER BY clause to the query.

        Indexes start at 1 in SQL!

        Note, you can use orderBy(DSL.val(1).desc()) or orderBy(DSL.literal(1).desc()) to apply descending ordering