Feedback
Did this article resolve your question/issue?

   

Article

How do the Connect for JDBC drivers handle result sets?

Information

 
TitleHow do the Connect for JDBC drivers handle result sets?
URL Namehow-do-the-connect-for-jdbc-drivers-handle-result-sets
Article Number000118356
EnvironmentProduct: Connect for JDBC Drivers
Version: All Supported
O/S: All Supported
Database: All Supported
Application: N/A
Question/Problem Description
How do the Connect for JDBC drivers handle result sets in general?  
Do the drivers perform any disk caching?
If the driver uses temporary files, where are they stored?

 

Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
Resolution
By default drivers do not read all the rows for the given query into memory. Instead, they read rows based on the client request in result set iteration.

Regarding Long data types (images, pictures, long text, binary data, or XML data ), if the data is not sufficient to keep in virtual memory, the drivers create temporary random files in the temp folder.

There are some connection options available for performance tuning based on the application requirements. Those are documented in the driver users's guide and can be found in the connection option descriptions as well as the performance section of the documentation.
Workaround
Notes
Last Modified Date1/14/2020 9:13 PM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.