t there are no resource leaks
>
> If you want to validate the behaviour, put some breakpoints into the
> source code of the PostgreSQL JDBC driver, or turn on debug logging of the
> driver. It should emit some debug information, e.g. in
> org.postgresql.core.v3.QueryExecutorImpl.send
Of course. Just one last question regarding Jooq if you don't mind.
With a Cursor I can understand how it works... Like, it maintains an open
ResultSet and you can fetch X records in a loop, do stuff with them and
repeat. But how does Jooq handles that with a stream ? Is it abstracted ?
You
Hi,
I'm not sure I'm using lazy fetching with streams correctly... I'm using
Jooq 3.9.6 en Postgresql 9.5.
This is my (simplified) repo method :
public Stream findLazy() {
return dslContext.select(...)
.fetchSize(100)
.fetchStream()
