Michael Hanselmann wrote:
>
> If there's only one parameter defined it takes
> that parameter as a lone parameter for a template query. The same
> function is used for the "SQLQueryParams&" variant. This creates a
> conflict where a template uses only one parameter. In that case, the
> logic doesn't work at all and the generated queries are unusable.
Yes, we know, it's already fixed in svn. You can read about the fix in
this message:
http://lists.mysql.com/plusplus/6435
This will be released as v2.2.2 soon.
How soon? Sooner if you test it and report favorably. :)
| Thread |
|---|
| • Conceptual issue in mysql++ 2.2.x (use(), store(), execute()) | Michael Hanselmann | 25 Mar |
| • Re: Conceptual issue in mysql++ 2.2.x (use(), store(), execute()) | Warren Young | 26 Mar |
| • Re: Conceptual issue in mysql++ 2.2.x (use(), store(), execute()) | Michael Hanselmann | 26 Mar |
| • Re: Conceptual issue in mysql++ 2.2.x (use(), store(), execute()) | Warren Young | 28 Mar |
| • Re: Conceptual issue in mysql++ 2.2.x (use(), store(), execute()) | Warren Young | 28 Mar |
| • Re: Conceptual issue in mysql++ 2.2.x (use(), store(), execute()) | Michael Hanselmann | 31 Mar |
| • Re: Conceptual issue in mysql++ 2.2.x (use(), store(), execute()) | Warren Young | 2 Apr |
| • Re: Conceptual issue in mysql++ 2.2.x (use(), store(), execute()) | Michael Hanselmann | 2 Apr |
| • Re: Conceptual issue in mysql++ 2.2.x (use(), store(), execute()) | Warren Young | 3 Apr |
| • Re: Conceptual issue in mysql++ 2.2.x (use(), store(), execute()) | Michael Hanselmann | 4 Apr |
| • Re: Conceptual issue in mysql++ 2.2.x (use(), store(), execute()) | Warren Young | 29 Mar |
