jOOQ 3.18.7 · org.jooq.LoaderLoadStep

The Loader API is used for configuring data loads.

The step in constructing the Loader object where you can execute the load.

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

Modifier and Type	Method and Description
public @NotNull Loader<R>	execute() Execute the load.

Method Detail

execute back to summary

execute	back to summary
public @NotNull Loader<R> execute() throws IOException Execute the load. All exceptions are caught and wrapped in the resulting `Loader` object. They can be accessed using `Loader#errors()` Annotations @NotNull @Support @Blocking

public @NotNull Loader<R> execute() throws IOException

Execute the load. All exceptions are caught and wrapped in the resulting Loader object. They can be accessed using Loader#errors()

Annotations

@NotNull
@Support
@Blocking

public Interface LoaderLoadStep<R extends org.jooq.Record>

Referencing `XYZ*Step` types directly from client code

Method Summary

Method Detail

public Interface LoaderLoadStep<R extends org.jooq.Record>

Referencing XYZ*Step types directly from client code

Method Summary

Method Detail

Referencing `XYZ*Step` types directly from client code