Flanders 0.18.3

Improved

• Binary columns are now readable. BINARY, VARBINARY, BLOB, BIT and spatial
  columns show a tidy placeholder such as [varbinary] instead of raw bytes, so
  a row of hashes or images no longer fills the grid with noise. The underlying
  value is untouched, so editing and primary-key matching keep working.
• A finessed Navicat import panel. The From Navicat window has been rebuilt
  around a live status card, a fixed footer whose Close button is always
  available, and a Stop button that halts a whole-drive search the instant you
  press it. Results stream in as they are found, with a running count and timer.

Flanders 0.18.2

Improved

• The Navicat backup search now shows what it's doing, live. As it looks it
  tells you which location it's scanning, streams each backup into the list the
  moment it's found, and shows a running count and timer. A whole-drive search
  can be stopped at any time.

Flanders 0.18.1

Added

• Search for Navicat backups anywhere. The Navicat import window now has a
  Search button that looks in the obvious places (Navicat's folder plus
  Documents, Desktop and Downloads), with a “Whole drive” option to search your
  home folder and mounted volumes too — handy if your backups have been moved.

Flanders 0.18.0

Added

• Import backups straight from Navicat. The Backup view has a new
  “From Navicat” button that finds the Navicat backups on your Mac for the
  current database and imports them into Flanders in one click — a simple way
  to bring your history across when you switch. Navicat's .nb3 backups are
  reconstructed faithfully (every table and row, binary data included), and you
  can also browse to a .nb3 file yourself.

Flanders 0.17.13

Fixed

• Restoring backups with binary data no longer corrupts it. Dumps that
  contain binary columns (for example WordPress/Wordfence tables keyed on a
  binary hash) are now restored byte-for-byte via the MySQL client when
  available, so values like binary primary keys come back exactly as they were.
  Plain text backups continue to use the fast built-in restore with full
  progress. Restore is also disabled until you're connected to a server.

Flanders 0.17.12

Fixed

• The About window's GitHub button now opens the public releases page.

Flanders 0.17.11

Added

• Choose whether a restore drops existing tables. The restore confirmation
  now has a “Drop existing tables first” switch. Leave it on (the default) to
  replace the data cleanly; turn it off to run the backup as-is and merge into
  what's already there. The dialog explains the effect of each choice.

Flanders 0.17.10

Fixed

• Restore is now reliable for standard mysqldump files. Two issues are
  resolved: statements preceded by a comment line (as mysqldump writes them) are
  no longer skipped during restore, and every table the backup defines is now
  cleared before restoring regardless of the dump's contents. Restoring a
  WordPress or other mysqldump backup now replaces the data cleanly instead of
  reporting "table already exists" and duplicate-key errors.

Flanders 0.17.9

Improved

• The backup log is now selectable, with Copy and Clear buttons. Select any
  part of the restore/backup log to copy it, or use the Copy button to grab the
  whole log at once — handy for keeping a record or sharing what happened.

Flanders 0.17.8

Fixed

• Restore now always replaces, so it can't duplicate your data. Backups made
  by other tools (for example a mysqldump without drop-table statements) used to
  be layered on top of the existing rows during a restore, duplicating
  everything. Flanders now clears each table the backup defines before restoring
  it, with foreign-key checks handled automatically — the restore replaces the
  data cleanly, exactly as the confirmation describes.