1. 09 Sep, 2019 3 commits
  2. 06 Sep, 2019 7 commits
  3. 05 Sep, 2019 5 commits
  4. 04 Sep, 2019 1 commit
  5. 03 Sep, 2019 2 commits
  6. 01 Sep, 2019 2 commits
  7. 30 Aug, 2019 3 commits
    • Vincent Pelletier's avatar
      ZMySQLDA.db: Close any replaced connection on reconnection. · 604e3ff3
      Vincent Pelletier authored
      MySQLdb relies on garbage collection to close the connection. Relying
      on such asynchronous event as the garbage collector is never a good idea,
      and this can cause issues when the transaction associated with the
      connection is started: because the connector is being replaced, it will
      never be properly aborted. So do not take chances and do not leak open
      connections: always close it.
      604e3ff3
    • Vincent Pelletier's avatar
      ZMySQLDA.db: Clarify that reconnection will only happen on actually closed connections. · 86849427
      Vincent Pelletier authored
      So that it's more apparent that we are not leaking a potentially active
      transaction on that connection.
      86849427
    • Vincent Pelletier's avatar
      ZMySQLDA.db: Drop special handling of syntax errors. · 29b30dc5
      Vincent Pelletier authored
      The same error code can be used for different causes. Specifically, it can
      be used for SQL-level syntax error (which this code intended to handle),
      or it can be used for fulltext syntax error (which makes this code raise).
      Also, drop forced-reconnection, because this means a still-established
      connection make be kept around and completely detected from current
      transaction, which may cause a database snapshot to be kept indefinitely
      (actually, until mariadb's timeout), in turn causing performance issue
      because of associated InnoDB snapshot.
      29b30dc5
  8. 29 Aug, 2019 2 commits
  9. 28 Aug, 2019 1 commit
  10. 16 Aug, 2019 5 commits
  11. 15 Aug, 2019 7 commits
  12. 13 Aug, 2019 2 commits