Execute the query and return a Map with one of the result's
columns as key and another one of the result's columns as value
Unlike fetchMap(Field, Field), this method allows for non-unique
keys in the result set.

Execute the query and return a Map with one of the result's
columns as key and another one of the result's columns as value
Unlike fetchMap(int, int), this method allows for non-unique
keys in the result set.

Execute the query and return a Map with one of the result's
columns as key and another one of the result's columns as value
Unlike fetchMap(Name, Name), this method allows for
non-unique keys in the result set.

Execute the query and return a Map with one of the result's
columns as key and another one of the result's columns as value
Unlike fetchMap(String, String), this method allows for
non-unique keys in the result set.

Execute the query and return a Map with one of the result's
columns as key and another one of the result's columns as value
An exception is thrown, if the key turns out to be non-unique in the
result set.

Execute the query and return a Map with one of the result's
columns as key and another one of the result's columns as value
An exception is thrown, if the key turns out to be non-unique in the
result set.

Execute the query and return a Map with one of the result's
columns as key and another one of the result's columns as value
An exception is thrown, if the key turns out to be non-unique in the
result set.

Execute the query and return a Map with one of the result's
columns as key and another one of the result's columns as value
An exception is thrown, if the key turns out to be non-unique in the
result set.

Depending on your JDBC driver's default behaviour, this may load the
whole database result into the driver's memory. In order to indicate to
the driver that you may not want to fetch all records at once, use
fetchLazy(int)

fetchLater

Deprecated.- 3.2.0 - [#2581] - This method will be removed in jOOQ 4.0

Fetch results asynchronously.

This method wraps fetching of records in a
Future, such that you can access the actual
records at a future instant. This is especially useful when

You want to load heavy data in the background, for instance when the
user logs in and accesses a pre-calculated dashboard screen, before they
access the heavy data.

You want to parallelise several independent OLAP queries before
merging all data into a single report

...

This will internally create a "single thread executor", that is shut down
at the end of the FutureResult's lifecycle. Use
fetchLater(ExecutorService) instead, if you want control over
your executing threads.

keepStatement

This indicates to jOOQ that the query's underlying Statement or
PreparedStatement should be kept open after execution. If it is
kept open, client code is responsible for properly closing it using
Query.close()

fetchSize

Regardless of this setting, fetchLazy() is the only way in jOOQ
not to fetch all data in memory. However, you may influence how your JDBC
driver interacts with your database through specifying a fetch size.