If my ResultSet contains CLOBs which take a long time to process, is it safe to iterate through ResultSet, put CLOBs in the queue and start processing them in multiple threads?
My hunch is that the CLOBs may be big enough to be swapped to disc (with default lob_buffer size), so, unless the driver deletes those temp files as I scroll through the resultSet (as opposed to deleting them then the resultset is closed) it should be possible to work with those inputstreams from multiple theads, correct?
Otherwise I'd be limited to processing just 1 row of CLOBs at a time...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If my ResultSet contains CLOBs which take a long time to process, is it safe to iterate through ResultSet, put CLOBs in the queue and start processing them in multiple threads?
My hunch is that the CLOBs may be big enough to be swapped to disc (with default lob_buffer size), so, unless the driver deletes those temp files as I scroll through the resultSet (as opposed to deleting them then the resultset is closed) it should be possible to work with those inputstreams from multiple theads, correct?
Otherwise I'd be limited to processing just 1 row of CLOBs at a time...