| List: | MySQL++ | « Previous MessageNext Message » | |
| From: | Kevin Regan | Date: | February 10 2006 5:49pm |
| Subject: | Strange result from query::execute()? | ||
| View as plain text | |||
Should the following have different results?
...
std::string s = "SET AUTOCOMMIT=1";
query.execute(s.c_str());
query.execute(s);
The first succeeds. The seconds throws an exception with the value "Query was empty."
Looking at the code, the first call goes to Query::execute(const char*). However, the
second uses a "parms" version of execute.
Is this expected behavior? From the library user's perspective, it seems confusing.
--Kevin
| Thread | ||
|---|---|---|
| • Strange result from query::execute()? | Kevin Regan | 10 Feb |
| • RE: Strange result from query::execute()? | Kevin Regan | 10 Feb |
| • Re: Strange result from query::execute()? | Warren Young | 10 Feb |
| • RE: Strange result from query::execute()? | Kevin Regan | 10 Feb |
