See the experimental [/timeline?n=100&r=reapply-conn-opts-on-clone|reapply-conn-opts-on-clone branch] for a possible fix.

I will merge this into trunk &mdash; which will become the next release &mdash; if it fixes your issue.

There is one thing that may be surprising about the change: it doesn't clone the previously applied option set if it's cloning a <i>disconnected</i> Connection, because that tracks the way reconnecting a disconnected connection behaves.

I can be talked into changing this if you need it to work differently because in the simple reconnection case, libmysqlclient is remembering the previously applied connection options, so MySQL++ doesn't have to reapply them. But with the clone, libmysqlclient doesn't understand what's going on, so it could be argued that MySQL++ should reapply the previously-applied connection objects in this particular case.