3 ms·

I don't disagree with any of that. My point is that I know sufficient SQL to do "stuff" in a database, and I don't have to go looking up documentation for \d wh

I don't disagree with any of that. My point is that I know sufficient SQL to do "stuff" in a database, and I don't have to go looking up documentation for \d when I'm using MySQL. SHOW DATABASES, SHOW TABLES is intuitive. \d (and being a unix guy, using \ rather than / is ... weird) is definitely not intuitive. Don't get me wrong, I've used Postgres when someone else has installed it for a project - it's a fine and capable database, and if I used it daily I'd probably get used to its syntax. It doesn't, however, seem to go out of its way to make things easier, IMHO. If you're going to have \dx as shortcuts for the typing-shy, then I don't see why you can't provide the more long-winded ones that don't require a manual lookup as well... I'm going to choose something that makes my life easier, when the line between one or the other choice is so fine - and MySQL is just ... easier.

petre 3y ago
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/
justinclift 3y ago
> SHOW DATABASES, SHOW TABLES is intuitive. For you. You've learned that and managed to internalise it. For me, "\d<whatever>" is intuitive. :)

petre 3y ago

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/

justinclift 3y ago

> SHOW DATABASES, SHOW TABLES is intuitive. For you. You've learned that and managed to internalise it. For me, "\d<whatever>" is intuitive. :)