I use both MySQL and Postgress. SHOW TABLES, SHOW CREATE TABLE, SHOW DATABASES is not SQL and takes too long to type. \dt, \df, \dv is very fast but I almost a

I use both MySQL and Postgress. SHOW TABLES, SHOW CREATE TABLE, SHOW DATABASES is not SQL and takes too long to type. \dt, \df, \dv is very fast but I almost always mess up. I think SQLite's .tables, .schema, .databases is a good middle ground. OTOH we have many connections writing to the database to many tables, so one process per connection is not necessarily to our advantage. We're still using MyISAM to store time series data because it's fast. Maybe Aria is a better replacement. Too bad MySQL or MariaDB doesn't have a time series extension like Postgres' TimescaleDB and the GIS functions are quite basic. On MariaDB, some of the useful functions compare the bounding box instead of the actual shape¹. MySQL 8 is somewhat better in this regard². It's good enough to store POIs but not great to intersect a linestring to multiple polygons and get a useful distance. Also no LISTEN/NOTIFY mechanism in MySQL. 1. https://mariadb.com/kb/en/mysqlmariadb-spatial-support-matrix/ https://mariadb.com/kb/en/mysqlmariadb-spatial-support-matri... 2. https://dev.mysql.com/blog-archive/geography-in-mysql-8-0/ https://dev.mysql.com/blog-archive/geography-in-mysql-8-0/