List:MySQL++« Previous MessageNext Message »
From:Warren Young Date:August 20 2010 4:25am
Subject:Re: execute() and store() discrepancy
View as plain text  
On Aug 19, 2010, at 9:42 PM, asokodesuka wrote:

> Le 20/08/2010 05:31, Warren Young a écrit :
>> execute() is for queries that do not return data per se.
> 
> And "this object also contains things like the number of rows that
> the query affected"
> 
> So why res.rows() is wrong ?

StoreQueryResult provides the num_rows() member function instead.

> Maybe using a SELECT with execute() should return an error ?

That would be something the underlying C API library would have to do, or more likely the
MySQL database server.  It doesn't, so MySQL++ doesn't.  The only robust way for MySQL++
to do this itself would be for it to contain a SQL parser, which just ain't gonna happen.

Thread
execute() and store() discrepancyasokodesuka20 Aug
  • Re: execute() and store() discrepancyWarren Young20 Aug
    • Re: execute() and store() discrepancyasokodesuka20 Aug
      • Re: execute() and store() discrepancyWarren Young20 Aug
        • Re: execute() and store() discrepancyasokodesuka20 Aug