MySQL++

Ticket Change Details
Login
Overview

Artifact ID: 77258d9fab7a0fe83f8fb7af42c8d41da6f01742f138c18b6183e275f8edeea1
Ticket: eab08a87eddde94ba8998f018d876e70a96e35d4
A Connection with options can't be duplicated.
User & Date: tangent 2018-07-12 21:44:43
Changes

  1. Change icomment to:

    See the experimental 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 disconnected 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.

  2. Change login to "tangent"
  3. Change mimetype to "text/x-fossil-wiki"
  4. Change priority to "Immediate"
  5. Change resolution to "Fixed"
  6. Change status to "Review"
  7. Change subsystem to "Library"