6 ms·

MySQL is a bit simpler even though pgadmin is a wonderful tool for learning postgres advantages. For me the difference became clear when needing to plot locatio

MySQL is a bit simpler even though pgadmin is a wonderful tool for learning postgres advantages. For me the difference became clear when needing to plot locations on a globe. PostGIS is super helpful

sam_lowry_ 6y ago
MySQL has way better UX for command line users. Postgres can't get away from legacy Ingres design, with a postgres user and a horrible command line client. Also, database/schema/tables hierarchy is a penalty over database/tables in MySQL.
- jasonpbecker 6y ago
  psql is easily one of my favorite tools. What makes the CLI "horrible" in your mind? Also, database/schema/tables is great when doing things like multi-tenancy where you split customers by schema (which also makes horizontal scaling super easy if needed).
  - syspec 6y ago
    I would say the commands are just not intuitive. For example, when you type quit instead of quitting it instead prints out that you must type a different command to quit
    - fire7000 6y ago
      One complaint is that it doesnt like camelCase identifiers
    - mattashii 6y ago
      Last time I tested (literally seconds ago) this works. All of \q, quit, and exit work fine starting psql 11?
      - syspec 6y ago
        Oh good to know!
    - majewsky 6y ago
      Ctrl-D works fine for me.
- mattashii 6y ago
  I fail to see how Postgres' hierarchy is any worse than MySQL. You have one more layer of hierarchy which you do not need to consume, with the added feature of atomic renaming any of the layers. If I'd compare this to MySQL, where you must move tables one-by-one to another schema (nay database) with the new name to 'rename' your database [0], then I'm very happy with postgres' hierarchy structure. [0] That is, if you're even allowed to, because if you have a trigger on your table, good luck renaming your database. See https://dev.mysql.com/doc/refman/8.0/en/rename-table.html https://dev.mysql.com/doc/refman/8.0/en/rename-table.html

MySQL is a bit simpler even though pgadmin is a wonderful tool for learning postgres advantages. For me the difference became clear when needing to plot locations on a globe. PostGIS is super helpful

sam_lowry_ 6y ago

MySQL has way better UX for command line users. Postgres can't get away from legacy Ingres design, with a postgres user and a horrible command line client. Also, database/schema/tables hierarchy is a penalty over database/tables in MySQL.

jasonpbecker 6y ago
psql is easily one of my favorite tools. What makes the CLI "horrible" in your mind? Also, database/schema/tables is great when doing things like multi-tenancy where you split customers by schema (which also makes horizontal scaling super easy if needed).
- syspec 6y ago
  I would say the commands are just not intuitive. For example, when you type quit instead of quitting it instead prints out that you must type a different command to quit
  - fire7000 6y ago
    One complaint is that it doesnt like camelCase identifiers
  - mattashii 6y ago
    Last time I tested (literally seconds ago) this works. All of \q, quit, and exit work fine starting psql 11?
    - syspec 6y ago
      Oh good to know!
  - majewsky 6y ago
    Ctrl-D works fine for me.
mattashii 6y ago
I fail to see how Postgres' hierarchy is any worse than MySQL. You have one more layer of hierarchy which you do not need to consume, with the added feature of atomic renaming any of the layers. If I'd compare this to MySQL, where you must move tables one-by-one to another schema (nay database) with the new name to 'rename' your database [0], then I'm very happy with postgres' hierarchy structure. [0] That is, if you're even allowed to, because if you have a trigger on your table, good luck renaming your database. See https://dev.mysql.com/doc/refman/8.0/en/rename-table.html https://dev.mysql.com/doc/refman/8.0/en/rename-table.html