List:MySQL++« Previous MessageNext Message »
From:Joel Fielder Date:January 13 2010 3:16pm
Subject:Re: Query::execute crashes without a connected driver
View as plain text  
Warren Young wrote:
> it probably affects much more than just execute(); exec(), store*(), 
> use()...  Maybe even high-level methods like insertfrom().
>
Have sorted these out on my local copy.

But, what to do about things like affected_rows and insert_id which 
return 0 if not connected but could be considered exceptional?

Also Query::escape_string(char*...) attempts the connected path when not 
connected so presumably this needs a check too?

Is there a bigger issue of "programmer's responsibility" here?
Thread
Query::execute crashes without a connected driverJoel Fielder7 Jan
  • Re: Query::execute crashes without a connected driverWarren Young7 Jan
    • Re: Query::execute crashes without a connected driverJoel Fielder8 Jan
    • mysqlpp::ScopedConnectionJoel Fielder8 Jan
      • Re: mysqlpp::ScopedConnectionWarren Young9 Jan
        • Re: mysqlpp::ScopedConnectionJonathan Wakely9 Jan
          • Re: mysqlpp::ScopedConnectionJoel Fielder11 Jan
            • Re: mysqlpp::ScopedConnectionJonathan Wakely11 Jan
              • Re: mysqlpp::ScopedConnectionWarren Young11 Jan
                • Re: mysqlpp::ScopedConnectionJonathan Wakely11 Jan
    • Re: Query::execute crashes without a connected driverJoel Fielder13 Jan
      • Re: Query::execute crashes without a connected driverWarren Young13 Jan
Re: mysqlpp::ScopedConnectionJoel Fielder11 Jan
  • Re: mysqlpp::ScopedConnectionWarren Young11 Jan
    • Re: mysqlpp::ScopedConnectionJoel Fielder11 Jan
      • Re: mysqlpp::ScopedConnectionWarren Young11 Jan
        • Re: mysqlpp::ScopedConnectionJoel Fielder12 Jan