Overview
Artifact ID: | 77258d9fab7a0fe83f8fb7af42c8d41da6f01742f138c18b6183e275f8edeea1 |
---|---|
Ticket: | eab08a87eddde94ba8998f018d876e70a96e35d4
A Connection with options can't be duplicated. |
User & Date: | tangent 2018-07-12 21:44:43 |
Changes
- icomment:
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 — which will become the next release — 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.
- login: "tangent"
- mimetype: "text/x-fossil-wiki"
- priority changed to: "Immediate"
- resolution changed to: "Fixed"
- status changed to: "Review"
- subsystem changed to: "Library"