List:MySQL++« Previous MessageNext Message »
From:Bassam A. Al-Khaffaf Date:February 8 2007 7:59am
Subject:RE: Strange error when to use MySQL++ 2.2.0 inplace of MySQL++ 2.1.1
View as plain text  
Thanks for your response. I wonder if it is considered a bug in the release
2.2.0. When my application runs at a Debug mode, it needs to show up the
query on the consol.

According to the documentation, the preview() has to be called up before
executing the query. So what can I do in this case. Shall I continue with
the previous release 2.1.1 or not. Is the latest release stable or not?

Your help is much appreciated.


Regards
Bassam


-----Original Message-----
From: Королев Илья [mailto:breeze@stripped] 
Sent: Thursday, February 08, 2007 3:09 PM
To: bassam@stripped
Subject: Re: Strange error when to use MySQL++ 2.2.0 inplace of MySQL++
2.1.1

Problem is in preview() call - it cause query 
corruption. You should not call preview() _before_ execute query.

> try
>
> {
>
> *radiusQuery << "SELECT c.profile_name, c.authentication_port,
> c.accounting_port, c.any_nas, s.secret_name, c.considration_id,
> r.considration_comment, c.log_verbosity, c.format_id, l.format_name,
> l.format_plugin\nFROM configurations_table AS c INNER JOIN
> (shared_secrets_table AS s, realm_considration_table AS r,
> logging_format_table AS l)\nON (c.secret_id = s.secret_id AND
> c.considration_id = r.considration_id AND c.format_id =
l.format_id)\nWHERE
> c.active_profile = true;";
>
>
>
>       cout << radiusQuery->preview() << endl << endl;
>
>
>
>       configResult = radiusQuery->store();
>
> }

-- 
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.432 / Virus Database: 268.17.29/673 - Release Date: 2/6/2007
5:52 PM
 

-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.432 / Virus Database: 268.17.29/673 - Release Date: 2/6/2007
5:52 PM
 

Thread
Strange error when to use MySQL++ 2.2.0 inplace of MySQL++ 2.1.1Bassam A. Al-Khaffaf8 Feb
  • Re: Strange error when to use MySQL++ 2.2.0 inplace of MySQL++ 2.1.1Jonathan Wakely8 Feb
RE: Strange error when to use MySQL++ 2.2.0 inplace of MySQL++ 2.1.1Bassam A. Al-Khaffaf8 Feb
  • Re: Strange error when to use MySQL++ 2.2.0 inplace of MySQL++ 2.1.1Warren Young8 Feb