Liya now accesses MySQL databases using the "caching_sha2_password “ method that is standard with MySQL 9.

This is a release with a new generation of "database connectors", built from MySQL 9.2.0 and PostgreSQL 17.4 sources, and the newer SQLite 3.49 sources. Built to make sure I can still continue to "manufacture" these connectors and keep Liya updated.

Liya now contains its own copies of the native MySQL and PostgreSQL “dump” binaries, together with the various “lib” files that they depend on, so that it can do MySQL and PostgreSQL import and export, whether the Mac itself (that Liya runs on) contains the full MySQL or PostgreSQL installation or not.

I have new MySQL and PostgreSQL installers for MacOS Sequoia available on the Liya web page at (https://cutedgesystems.com/software/Liya/). This Liya update keeps Liya's database import and export functions in sync with these new database installers (especially for PostgreSQL).

Liya now uses native MySQL and PostgreSQL export and import commands — but the export and import functions will only work if /usr/local/mysql (on the machine Liya is running on) contains or points to a MySQL installation and /usr/local/pgsql contains or points to a PostgreSQL installation. They will export and import .mysql and .pgsql dump files. Liya can create users with full privileges on the local MySQL or PostgreSQL installation, that can access the database from anywhere, remotely. And you can change these passwords at any time using Liya. This version of Liya still runs on MacOS 10.13 (High Sierra) onwards.

MySQL exports now use the bin/mysqldump command to produce the .mysql dump files, whereas imports use the bin/mysql command to import from the .mysql exported files. This will make MySQl imports and exports in Liya work predictably and consistently with what one would expect from using the MySQL command line.

Improved MySQL import from exported MySQL dump files.

This version now works also with MySQL 9.x, including the creation of new MySQL users and passwords.

Updated to include SQLite 3.45.3

User interface bug fix. The OK button was inadvertently occluded by an invisible UI element, making it sometimes difficult to detect a mouse click. This is fixed in this version.

Fixed the user interface to make the app look better in Dark Mode.

This is the first version that is complied as a fat binary (for ARM and Intel-based Macs).

Liya calculates timestamp for SQLite from 1st January 1970, if the data is stored as an integer or real number rather than a date string.

This version works with MySQL 8 and PostgreSQL 11 databases.

Some minor user interface bug fixes

General bug fixes. Also, for custom SQL commands, the column order will now follow the given Select statement.

Minor bug fixes

Bug fix: Custom SQL Command field didn't allow the use of the Character Input Menu, e.g., to choose Pinyin to enter Chinese characters into the SQL query string. This has been fixed. Made MySQL connections work more like PostgreSQL connections, in terms of the choice of character set used. The character set used in each connection to the database follows that of the database. If at the point of the connection, no database has been chosen, then the connection defaults to using UTF8. New databases in Liya are created using UTF8 as the default character set. Also fixed a crash while importing and exporting databases that occurred after version 3.0.3, when Liya was made to be Sandbox-compliant.

Minor bug fixes.

This a bumper bug fix release. Fixed some of the more quirky user-interface oddities, so it’ll work as modelessly (and smoothly) as I can make it. This is the first version to get iCloud support. You can share SQLite files in iCloud with the iPad version of Liya. Fixed a bug in the Query field where the smart quotes get in the way of entering custom SQL commands. Also, at some point, MySQL stopped allowing the time zone to be included in a timestamp field. Updated Liya to handle this rejection more gracefully. Finally, one oft-requested feature - Liya now reports SQL command line errors when users run custom SQL commands (or when Liya has a bug). I’ve made so many changes in this version that I could have introduced even more bugs. As usual bug reports are very welcome.

The Mac Sandbox requires the Open Panel to be used for navigating to SQLite files, and so the URL and Database Name fields, in Liya 3.0, were locked from editing to force the user to use the Open Panel. However, if the user has Command-copied a path to a SQLite file (onto the pasteboard), Liya 3.0.1 now allows the user to Control-Click on the URL field to get a contextual menu that allows the URL to be pasted into the URL field, which then helpfully opens the Open Panel at the correct URL, thus restoring the pre-3.0 copy-and-paste functionality, while still meeting the requirements of the Sandbox. Plus, there are other bug fixes. Enjoy...

This version works with the Mac App Sandbox. Also provides support for SQLite dates created by Core Data. Plus some bug fixes.

General bug fixes. SQLite data handling improved for 64 bit large integers.

Fixed Liya so it'll handle SQLite fields declared as Real. Also added .sql and .sqldb to the document file types (a set which includes sqlite, sqlite3 and db) that will automatically launch Liya.

Fixed Liya so it'll handle SQLite fields declared as Bool. Liya will treat it as an integer, and map it to the Cocoa NSNumber data type. Also, while it was always possible to drag and drop Liya table contents data onto a spreadsheet like Numbers, this version makes it easier by turning on also copy and paste. Liya will now also show the version number of the MySQL, MariaDB or PostgreSQL database that it is connecting to in the title of the connection window.