| List: | MySQL++ | « Previous MessageNext Message » | |
| From: | Joel Fielder | Date: | January 13 2010 3:16pm |
| Subject: | Re: Query::execute crashes without a connected driver | ||
| View as plain text | |||
Warren Young wrote: > it probably affects much more than just execute(); exec(), store*(), > use()... Maybe even high-level methods like insertfrom(). > Have sorted these out on my local copy. But, what to do about things like affected_rows and insert_id which return 0 if not connected but could be considered exceptional? Also Query::escape_string(char*...) attempts the connected path when not connected so presumably this needs a check too? Is there a bigger issue of "programmer's responsibility" here?
| Thread | ||
|---|---|---|
| • Query::execute crashes without a connected driver | Joel Fielder | 7 Jan |
| • Re: Query::execute crashes without a connected driver | Warren Young | 7 Jan |
| • Re: Query::execute crashes without a connected driver | Joel Fielder | 8 Jan |
| • mysqlpp::ScopedConnection | Joel Fielder | 8 Jan |
| • Re: mysqlpp::ScopedConnection | Warren Young | 9 Jan |
| • Re: mysqlpp::ScopedConnection | Jonathan Wakely | 9 Jan |
| • Re: mysqlpp::ScopedConnection | Joel Fielder | 11 Jan |
| • Re: mysqlpp::ScopedConnection | Jonathan Wakely | 11 Jan |
| • Re: mysqlpp::ScopedConnection | Warren Young | 11 Jan |
| • Re: mysqlpp::ScopedConnection | Jonathan Wakely | 11 Jan |
| • Re: Query::execute crashes without a connected driver | Joel Fielder | 13 Jan |
| • Re: Query::execute crashes without a connected driver | Warren Young | 13 Jan |
| • Re: mysqlpp::ScopedConnection | Joel Fielder | 11 Jan |
| • Re: mysqlpp::ScopedConnection | Warren Young | 11 Jan |
| • Re: mysqlpp::ScopedConnection | Joel Fielder | 11 Jan |
| • Re: mysqlpp::ScopedConnection | Warren Young | 11 Jan |
| • Re: mysqlpp::ScopedConnection | Joel Fielder | 12 Jan |
