At 19/10/2002 19:16, Venu wrote:
> Its because of mysql_store_result(), instead you should
> check the option 'Don't cache results' to use
> 'mysql_use_result()'.
I tried to uncheck the option " Don't cache results " (with MyODBC 3.51.04 it is
" Don't cache Results(only for forward-only cursor)
At 19/10/2002 22:08, Patrick Sherrill wrote:
> It sounds like it may be time to look at threads. Set up a thread and open
> your recordset there or look at the C or C++ API for MySQL.
It's not a thread problem.
Thanks,
Massimo.
-
This mail se
At 19/10/2002 17:17, Ed Carp wrote:
> It's not a MySQL problem, but a problem how you're opening the recordset.
> In VB, you would set the DBSQLPassThru flag - I don't know what the
> equivalent is in Windows C. The problem is that the client is downloading
> the entire record set and oding the se
It sounds like it may be time to look at threads. Set up a thread and open
your recordset there or look at the C or C++ API for MySQL.
Pat...
[EMAIL PROTECTED]
CocoNet Corporation
SW Florida's 1st ISP
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday,
Hi !!!
> Hi all
>
> I'm having a performance problem opening a recordset using a
> CRecordset class (Visual C++). If the table is empty (or
> contains few records) it takes a very little time to open,
> but if the table contains many records (about 48000 in my
> tests) it takes too much time
> Does anybody know how I can solve this problem?
> How can I improve the " opening " performance?
> Does MySQL cache something for each records?
It's not a MySQL problem, but a problem how you're opening the recordset.
In VB, you would set the DBSQLPassThru flag - I don't know what the
equivalent
Well, let's start with the simply, yet possibly overlooked solution: have
you indexed the table appropriately?
Mike Hillyer
-Original Message-
From: [EMAIL PROTECTED] [mailto:m.colurcio@;softhor.com]
Sent: Saturday, October 19, 2002 9:12 AM
To: [EMAIL PROTECTED]
Subject: Slow opening a re
