Could it be that you have too many results or huge objects in the result. Debug the SQL in
mysql client.
I have used StoreQueryResults and never have had any issues like what you are having.
.. dk
----- Reply message -----
From: "Paul Dalach" <pdalach@stripped>
To: "plusplus@stripped" <plusplus@stripped>
Subject: StoreQueryResults destructor runs without end...
Date: Tue, Mar 22, 2011 22:43
Hi everyone,
Okay, so I lied a bit...the destructor merely takes 4-6 minutes to
finish after it goes out of scope.
Is this normal behavior? I can't imagine it is. Has anyone else
experienced this issue and, if so, how can it be fixed?
Thanks,
Paul Dalach
--
MySQL++ Mailing List
For list archives: http://lists.mysql.com/plusplus
To unsubscribe: http://lists.mysql.com/plusplus?unsub=1

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.