List:MySQL++« Previous MessageNext Message »
From:Warren Young Date:March 26 2007 12:28pm
Subject:Re: Conceptual issue in mysql++ 2.2.x (use(), store(), execute())
View as plain text  
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 Hanselmann25 Mar
  • Re: Conceptual issue in mysql++ 2.2.x (use(), store(), execute())Warren Young26 Mar
    • Re: Conceptual issue in mysql++ 2.2.x (use(), store(), execute())Michael Hanselmann26 Mar
      • Re: Conceptual issue in mysql++ 2.2.x (use(), store(), execute())Warren Young28 Mar
        • Re: Conceptual issue in mysql++ 2.2.x (use(), store(), execute())Warren Young28 Mar
        • Re: Conceptual issue in mysql++ 2.2.x (use(), store(), execute())Michael Hanselmann31 Mar
          • Re: Conceptual issue in mysql++ 2.2.x (use(), store(), execute())Warren Young2 Apr
            • Re: Conceptual issue in mysql++ 2.2.x (use(), store(), execute())Michael Hanselmann2 Apr
              • Re: Conceptual issue in mysql++ 2.2.x (use(), store(), execute())Warren Young3 Apr
                • Re: Conceptual issue in mysql++ 2.2.x (use(), store(), execute())Michael Hanselmann4 Apr
Re: Conceptual issue in mysql++ 2.2.x (use(), store(), execute())Warren Young29 Mar