13 messages in com.mysql.lists.plusplusRe: Issues with multi-queries| From | Sent On | Attachments |
|---|---|---|
| Paul Martin | 07 Nov 2007 09:30 | |
| Warren Young | 07 Nov 2007 12:56 | |
| Paul Martin | 07 Nov 2007 13:05 | |
| Warren Young | 07 Nov 2007 13:38 | |
| Paul Martin | 07 Nov 2007 15:06 | |
| Warren Young | 07 Nov 2007 16:07 | |
| Maarten Schrijvers | 08 Nov 2007 03:22 | |
| Paul Martin | 08 Nov 2007 14:33 | |
| Warren Young | 09 Nov 2007 15:02 | |
| Paul Martin | 09 Nov 2007 18:31 | |
| Warren Young | 09 Nov 2007 19:10 | |
| Ian Daysh | 12 Nov 2007 01:10 | |
| Warren Young | 12 Nov 2007 22:12 |
| Subject: | Re: Issues with multi-queries |
|---|---|
| From: | Warren Young (mysq...@etr-usa.com) |
| Date: | 11/07/2007 04:07:07 PM |
| List: | com.mysql.lists.plusplus |
Paul Martin wrote:
My point is not to debug my own code,
Are you certain that it isn't bugs in your code that are causing the problem, then?
This is the first message I remember seeing on this list in the 2+ years we've supported multiqueries that suggests that they just don't work. Either you're the first to really use them, or your code has a bug.
The endl's are used because the original multiquery example used them.
Ah. We had them in there only to make the preview() calls prettier. I've removed them.
I've just modified a simple example to show it break.
You haven't "shown" anything. You've just stated that "this is the case" with no proof. What you posted doesn't compile and run, and neither I nor probably anyone else is going to take the time to change it until it does break, if only because you can't prove that something _doesn't_ happen. It's up to you to prove that it _does_.
You have to meet us more than halfway on this. We're unpaid volunteers.
I suppose I could use the sample db but that might not behave the same.
I addressed this in my previous email: if it doesn't behave the same, that tells you something interesting and useful. It's a legitimate troubleshooting step, totally separate from the matter of making it convenient for people to test things for you on their machines.
I have a feeling the engine isn't ready for another call for a short time,
Some of the biggest sites on the net run on MySQL. These sites see normal loads of thousands of queries per second, and I assure you, they don't have magic delays between every query. If that were necessary, MySQL wouldn't have achieved its present popularity, and even if it had, MySQL++ would either do this internally for you or tell you to do it in the user manual.
It looks like there may be a memory leak issue as well,