From: Kevin Regan
Date: June 25 2009 5:02pm
Subject: RE: Issue with ReconnectOption
List-Archive: http://lists.mysql.com/plusplus/8647
Message-Id: <4B18A8F75A6384449755BC7784073E9360CF02E1BD@exch11.olympus.f5net.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

My bad -- I see this now.  This change should work for me.

--Kevin

-----Original Message-----
From: Warren Young [mailto:mysqlpp@stripped]=20
Sent: Wednesday, June 24, 2009 10:50 PM
To: plusplus@stripped
Subject: Re: Issue with ReconnectOption

[reordered conversation to be in logical order...]

>> Kevin Regan wrote:
>>> It seems that the dbd->connected() check should only be performed =20
>>> for
>>> versions of MySQL greater than 5.1.6.
>>
>> Isn't that backwards?  As I read your reference manual excerpt, after
>> the fix in 5.1.6, you can set this option at any time, and it will be
>> set as expected.  It's only with the older versions, where the option
>> handling had the bug, where we should check for a connection before
>> allowing the option to be set

> No, the issue is that the current mysql++ code does not allow me (at =20
> v5.0.64) to set the reconnect option after the connection is =20
> established.

I think you didn't read my patch very carefully.  It changes MySQL++ =20
so that for versions 5.0.13 (where the option was introduced in the C =20
API) through 5.1.6 (where its effect changed) the option can only be =20
applied when there is a connection.  There is no point in allowing the =20
option to be set before the connection comes up for this range of =20
versions, since as you point out, it will be reset when the connection =20
comes up.

Apply it and try it.  Does it not do what you want?

> Any word on this?

I've been out of town for a bit over a week, on vacation, totally =20
disconnected from networks of all kinds.

--=20
MySQL++ Mailing List
For list archives: http://lists.mysql.com/plusplus
To unsubscribe:    http://lists.mysql.com/plusplus?unsub=3Dk.regan@stripped