[#1001213] In VisualBasic, opening cursors using adUseClient takes a very long time

Date:
2007-01-04 14:12 Priority:
3

State:
Open

Submitted by:
Barbara Epis (bepis) Assigned to:
Nobody (None)

Category:
Incorrect behavior Group:

Resolution:
None

Summary:
In VisualBasic, opening cursors using adUseClient takes a very long time

Detailed description
In VisualBasic, opening cursors using adUseClient takes a very long time. e.g.: to open an adUseClient cursor on a table containing 1000 records takes 2.5 minutes against the few seconds of the ODBC driver. Environment: Windows XP SP2 VB 6 SP5 and ADO PostgreSQL 8.03 OLE DB provider 1.0.0.20 Table: CREATE TABLE testtable1 ( id serial NOT NULL, descr varchar(255), annot text ) Code: Dim strSql As String Dim conn As New ADODB.Connection Dim rs As New ADODB.Recordset conn.Open "Provider=PostgreSQL OLE DB Provider;Password=xxx;User ID=test;Data Source=localhost;Location=test;Extended Properties=""""" strSql = "SELECT * FROM testtable1" rs.CursorLocation = adUseClient rs.CursorType = adOpenStatic rs.LockType = adLockReadOnly rs.ActiveConnection = conn rs.Source = strSql rs.Open ' 2:30 minuts rs.Close

Followup

Message
Date: 2007-05-02 14:37 Sender: Victor Snezhko Hello, barbara, Opening cursor in client cursor mode equals to reading the whole table contents to the Microsoft CCE's local cache. This is expected to take a long time if you texts contain large amounts of data. Are you sure you have turned on the equivalent of this setting in ODBC, to compare fairly?
Date: 2007-04-23 01:32 Sender: hensa hensa if you'd work on OLE DB provider 1.0.0.19 no problem about too many time

No Changes Have Been Made to This Item