Whether 80k records is huge or not, I would leave that for experts on this list.
To be honest, I've never had to deal with such huge recordset with mysql++.
What I can suggest is to debug or add debug logging to the library to see where it is
spending time.
Bests
Dk
----- Reply message -----
From: "Paul Dalach" <pdalach@stripped>
To: "Dino Korah" <dino.korah@stripped>
Cc: "plusplus@stripped" <plusplus@stripped>
Subject: StoreQueryResults destructor runs without end...
Date: Wed, Mar 23, 2011 00:49
Thanks for replying!
I am pulling ~80k objects with four fields. Does that constitute huge?
If it does, what is the solution?
The MYSQL database itself is fine...we can use the client or draw using
the matlab connector without issue.
Paul
On 3/22/2011 5:51 PM, Dino Korah wrote:
> 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
>
>
