List:MySQL++« Previous MessageNext Message »
From:Warren Young Date:January 28 2009 1:26am
Subject:Re: query.str() in template query -- <blush>
View as plain text  
Jim Wallace wrote:
> 
> It'd be cool if this abuse could be detected at compile time instead
> of runtime.

Suggestions as to how?

I wouldn't be averse to adding an exception for this.  That puts 
detection off to runtime, but it's then impossible to mistake for a 
MySQL++ bug.

I'm also willing to accept patches that allow this brokenness to work 
*as long as* they don't break something else.  That's the main reason we 
don't claim to support this: it's interfered with other things in the 
past, usually due to some C++ restriction on overloading.  Since the 
Query::template_defaults mechanism is meant for other things, I didn't 
shed a tear when learning that it can't be used to completely fill out a 
query in all situations.
Thread
RELEASE: v3.0.5Warren Young7 Aug
  • query.str() in template query -- help!Jim Wallace28 Jan
    • RE: query.str() in template query -- <blush>Jim Wallace28 Jan
      • Re: query.str() in template query -- <blush>Warren Young28 Jan
        • storein with parametersJim Wallace28 Jan
          • Re: storein with parametersWarren Young28 Jan
            • RE: storein with parametersJim Wallace28 Jan
              • Re: storein with parametersWarren Young28 Jan
            • Question about BadQueryJim Wallace28 Jan
              • Re: Question about BadQueryWarren Young28 Jan
RE: RELEASE: v3.0.5Bernard8 Aug
  • Re: RELEASE: v3.0.5Warren Young8 Aug
    • Re: RELEASE: v3.0.5Alex9 Aug
RE: Question about BadQueryJim Wallace28 Jan
RE: Question about BadQueryDale Stewart28 Jan
RE: Question about BadQueryDale Stewart28 Jan
  • Re: Question about BadQueryWarren Young28 Jan