LoaderLoadStep (jOOQ 3.12.1 API)

All Known Subinterfaces:

LoaderCSVOptionsStep<R>, LoaderJSONOptionsStep<R>, LoaderListenerStep<R>
```
public interface LoaderLoadStep<R extends Record>
```
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
Author:

Lukas Eder

- Method Summary
  
  All Methods Instance Methods Abstract Methods
  Modifier and Type Method Description
  
  Loader<R> execute()
  Execute the load.

- Method Detail
  - execute
```
@Support
Loader<R> execute()
           throws java.io.IOException
```
    Execute the load. All exceptions are caught and wrapped in the resulting Loader object. They can be accessed using Loader.errors()
    
    Throws:
    
    java.io.IOException