5 ms·
Really a shame they used the mysql protocol. The mysql command line client is terrible compared to psql, and the mysql lib is much less pleasant to use than li
by asdasf 13y ago
Really a shame they used the mysql protocol. The mysql command line client is terrible compared to psql, and the mysql lib is much less pleasant to use than libpq.
- AaronBBrown 13y agoCan you give an example of where mysql (the client) is terrible compared to psql (the client)? I've had the opposite experience.
- cdavid 13y agofor once, you get proper reverse search, which is not available in mysql (last time I checked, which has now been a while TBH).
- meritt 13y agomysql cli has always had reverse search (ctrl+r) because it was built on readline. They actually recently disabled it, indirectly, because they switched to editline. So now you gotta configure it via ~/.editrc http://bugs.mysql.com/bug.php?id=60465 http://bugs.mysql.com/bug.php?id=60465
- AaronBBrown 13y agoWorks for me. I use this feature nearly all day. http://showterm.io/03de0c8a4992dc7008ef2 http://showterm.io/03de0c8a4992dc7008ef2
- asdasf 13y agoUseful tab completion, more useful commands, catching Ctrl+C like a shell is supposed to do instead of exiting like an asshole, etc. Can you give an example of your opposite experience? I've literally never met someone who has used both and not preferred psql before.
- jamiesonbecker 13y agoMySQL is ubiquitous, pgsql less so. Most cross-db tools start with MySQL compatibility first. Regardless of whether a given tool is better for some use case, targeting compatibility with the market leader makes all kinds of sense.