All Versions
42
Latest Version
Avg Release Cycle
88 days
Latest Release
1116 days ago

Changelog History
Page 1

  • v0.9.1 Changes

    November 16, 2018
    • ๐Ÿ› Bug fix
      • Encode timestamps as DateTime (for now currently required to be in UTC) when opting into the new calendar types
  • v0.9.0 Changes

    November 01, 2018
    • โœจ Enhancements

      • Support Elixir 1.3 Calendar types
      • Support polygon types
      • Support JSON type
      • Support unix sockets
      • Support transaction status propagation from database
      • Update to DBConnection 2.0.0
    • ๐Ÿ› Bug fixes

      • Fix ping error handling
  • v0.9.0-rc.0

    October 14, 2018
  • v0.8.4

    February 05, 2018
  • v0.8.3 Changes

    August 11, 2017
    • โœจ Enhancements

      • use CLIENT_DEPRECATE_EOF flag to make decision about EOF messages
      • travis tests on different mariadb/mysql versions
      • introduce :query_type prepare option
      • fix typo in protocol handle_declare
    • ๐Ÿ› Bug fixes

      • fix close socket when disconnect failed
      • do disconnect on handshake error
  • v0.8.2 Changes

    March 27, 2017
    • โœจ Enhancements

      • remove warnings for elixir v1.4
    • ๐Ÿ› Bug fixes

      • fix some bugs on reconnection
  • v0.8.1 Changes

    December 08, 2016
    • โœจ Enhancements

      • better performance on decoding multiple rows
      • add support for non-microsecond datetimes
    • ๐Ÿ› Bug fixes

      • fix error when executing a stored procedure that does not return any results
  • v0.8.0 Changes

    November 16, 2016
    • โœจ Enhancements

      • add MDBPORT enviroment
      • add streaming support
    • Backwards incompatible changes

      • remove support of elixir < 1.2
  • v0.7.9 Changes

    November 08, 2016
    • โœจ Enhancements

      • different performance optimization of query handling
    • ๐Ÿ› Bug fixes

      • fix truncate query
  • v0.7.8 Changes

    September 16, 2016
    • โœจ Enhancements
      • add tls support
      • add option for switching, how strings are saved in database