|
Information Technologies
 |
Problem of the jConnect JDBC Driver by Sybase In order to support scrollable cursors, jConnect caches the row data on the client - the entire result set is stored in the client memory!!!
The following is from the reference: "jConnect uses the Tabular Data Stream (TDS)--the Sybase proprietary protocol--to communicate with Sybase database servers. As of jConnect 6.0, TDS does not support scrollable cursors. To support scrollable cursors, jConnect caches the row data on demand, on the client, on each call to ResultSet.next. However, when the end of the result set is reached, the entire result set is stored in the client memory. Because this may cause a performance strain, Sybase recommends that you use TYPE_SCROLL_INSENSITIVE result sets only when the result set is reasonably small" | |||
|
The Home of Mini SQL (mSQL) | |
Database Programming with JDBC and Java | |
|
Databases for Web Developers | |
Oracle8i JDBC Developer's Guide and Reference | |
|
PostgreSQL | |
Linux SQL Databases and Tools | |
|
Perl and SQL Databases | |
Programming the Perl DBI | |
|
Oracle and SAP | |
The MySQL Reference Manual | |
|
MySQL & mSQL with Perl | |
Oracle Essentials: Introducing Oracle | |
|
Object Data Management Group | |
DB2 Universal Database Version 7.x Manuals | |
|
SQL Functions | |
DKG Advanced Solutions, Inc. | |
|
DB2 SQLCODE List | |
Oracle Essentials: Multiuser Concurrency | |
|
Oracle 8.1.6 Documentation | |
Oracle 8.1.7 Documentation | |
|
MySQL 3.2x Documentation [Mirror] [Mirror] [Mirror] [Mirror] [Mirror] | |||
|
|