MYSQL Release Notes
  • 13 Jun 2024
  • 1 Minute to read
  • Dark
  • PDF

MYSQL Release Notes

  • Dark
  • PDF

Article summary

June 2024

Panoply now supports extraction of deleted records using the Binary Logs. When Binary Logs is enabled, Panoply will identify deleted records (on top of the new and updated ones) and will update them accordingly in Panoply. Every deleted record from MySQL will have the value true on the __deleted column in the Panoply table.

December 2021 (v 2.4.0)

Collecting data using binary logs is now available. In order to use binary logs in your data source you need to:

  • Have binary logs enabled on the MySQL server:
    • Server version 5.5. and higher
    • Binary logs are enabled on the MySQL server (The log is enabled by starting the server with the --log-bin option)
    • server_id should be set to non-zero value (read more)
    • binlog_format should be set to ROW (read more)
    • row_image should be set to FULL(read more)
    • The following permissions should be set on the connected user:
      • SELECT permission on the database;
      • REPLICATION CLIENT or SUPER permission;
      • REPLICATION SLAVE permission.
  • Enable binary logs in the advanced options

Once the binary logs is enabled in Panoply, only tables will be available for selection.

May 2021

SSH support has been added for MySQL.

March 2021

The option to login using SSL has been added to the UI for MySQL.

January 2021

Panoply fixed a bug that was returning null values in columns that should not be null.

Panoply fixed a bug preventing collection of the data source following migration to V 2.0.

October 2020

Panoply has refreshed the MySQL data source and is opening it up to public beta. As a part of this refresh, a number of bug fixes were also addressed. For more information, see MySQL Documentation.

Panoply will migrate all instances of MySQL in your data warehouse. For more information about this migration, see Supplemental Release Notes for MySQL.

Was this article helpful?