| List: | MySQL++ | « Previous MessageNext Message » | |
| From: | Jim Wallace | Date: | January 28 2009 3:55am |
| Subject: | Question about BadQuery | ||
| View as plain text | |||
Would it be possible to store the failed query in the exception? That way if I have multiple statements in a try/catch I could figure out which one caused the exception. I'd be willing to add the feature if you think it was useful and feasible. Right now we have a trace log we can turn on that does a query.str(...) on each query before it runs, that way we can capture the bad query if an exception is thrown, but we don't always have it turned on to avoid flooding the logs, which is a problem on one-time errors. jmw
| Thread | ||
|---|---|---|
| • RELEASE: v3.0.5 | Warren Young | 7 Aug |
| • query.str() in template query -- help! | Jim Wallace | 28 Jan |
| • RE: query.str() in template query -- <blush> | Jim Wallace | 28 Jan |
| • Re: query.str() in template query -- <blush> | Warren Young | 28 Jan |
| • storein with parameters | Jim Wallace | 28 Jan |
| • Re: storein with parameters | Warren Young | 28 Jan |
| • RE: storein with parameters | Jim Wallace | 28 Jan |
| • Re: storein with parameters | Warren Young | 28 Jan |
| • Question about BadQuery | Jim Wallace | 28 Jan |
| • Re: Question about BadQuery | Warren Young | 28 Jan |
| • RE: RELEASE: v3.0.5 | Bernard | 8 Aug |
| • Re: RELEASE: v3.0.5 | Warren Young | 8 Aug |
| • Re: RELEASE: v3.0.5 | Alex | 9 Aug |
| • RE: Question about BadQuery | Jim Wallace | 28 Jan |
| • RE: Question about BadQuery | Dale Stewart | 28 Jan |
| • RE: Question about BadQuery | Dale Stewart | 28 Jan |
| • Re: Question about BadQuery | Warren Young | 28 Jan |
