From: Warren Young
Date: November 13 2008 5:13pm
Subject: Re: MySQL 5.0.67, mysql++ 2.3.2, and Rational Rose RT 7.1
List-Archive: http://lists.mysql.com/plusplus/8137
Message-Id: <491C603C.2090305@etr-usa.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Van Note, Ryan - SSD wrote:
> First, is mysql++ 2.3.2 compatible with MySQL 5.0.67?

If it isn't, this would be the first I've heard about it, and 5.0.67 has 
been out for quite some time now.  The odds are against there being an 
incompatibility.

> My application was using a static member attribute
> for containing the database connection (MySqlConnection
> dbConnection), and it appeared that the failed connection crash was
> the result of the connection attribute not being cleaned up properly
> after a failed connection.

We can't help you debug classes we didn't write.  If you want help, you 
need to boil your problem down to an example we can try here.

Do the MySQL++ examples work?  If so, that suggests the bug is in your 
code.  Try to modify the examples to reproduce the problem you're seeing.

> try { databaseConnection = NULL;
> 
> databaseConnection = new MySqlConnection();
> 
> databaseConnection->connect( rtdata->database.c_str(), 
> rtdata->hostname.c_str(), rtdata->username.c_str(), 
> rtdata->password.c_str(), 0, 0, CONNECT_TIMEOUT, 0, 
> CLIENT_MULTI_STATEMENTS );
> 
> }
> 
> catch(MySqlConnectionFailed error) { // Determine if the
> databaseConnection // handle is valid. if( databaseConnection ) { 
> delete databaseConnection; databaseConnection = NULL; } }

Just repeating for clarity: none of this code is meaningful to anyone 
here but you.  We didn't write it, we can't compile it, so we're not 
going to try to debug it.

> mysql_ping() call within the MySQL
> 5.0.67 library is what is actually failing, not mysql++ nor my code.

Take it up on the main MySQL list, where the C API is on topic.