3 ms·
MySQL doesn't excite me at all anymore. It used to be my DB of choice but as of late I've been using postgres and other than tools being somewhat lacking (this
by joshstrange 12y ago
MySQL doesn't excite me at all anymore. It used to be my DB of choice but as of late I've been using postgres and other than tools being somewhat lacking (this is getting better all the time, there are now GUI browsers for postgres that rival sequel pro). Nothing was really keeping me on MySQL other than it was generally the prefered DB for most OS projects and I had used it in professional settings multiple times. Postgres's JSON store is very interesting and I've read a number of articles on other cool things in Postgres all while MySQL was more or less silent. I'd love to setup a postgres server at work and benchmark it against our MySQL DB, the one thing really holding me back is our use of ENUMs but I don't think that's going to be a big barrier and I hate them anyways.
- pilif 12y ago> the one thing really holding me back is our use of ENUMs but I don't think that's going to be a big barrier and I hate them anyways Postgres has proper support for ENUM as defined in the SQL Standard. You have to create a new type and declare it as being an ENUM type: http://www.postgresql.org/docs/9.4/static/datatype-enum.html http://www.postgresql.org/docs/9.4/static/datatype-enum.html
- joshstrange 12y agoVery interesting! Thanks for the link, even with that I'd rather convert the ENUMs to just VARCHARs as our MVC framework doesn't support ENUMs but it "Just works" because it sends strings to MySQL and MySQL stores them as INTs that map to ENUM values. Because of this the test framework never played nice with creating test DB's that used ENUMs.
- recibe 12y agoPostgres' ecosystem is a joke compared to mysql's. Just try finding a: - mysql-to-postgres import tool - mysql workbench for postgres (pgadmin is terrible) - phpmyadmin replacement for postgres (phpPgAdmin is terrible)
- eropple 12y agoI know what you're saying, but when I hear people being excited about data stores, I get a little worried. (Being excited about data stores gave us the rise of MongoDB. MySQL tables corrupting because you used MyISAM like a well-intentioned fool is "exciting", too.) I've moved to Postgres for most things because it's not at all exciting for the majority of use cases. It does a thing, does it well, and doesn't break. I honestly can't say the same about MySQL.
- joshstrange 12y agoYes, "Excite" is probably not the right word to use there. I share a wariness towards too much "excitement" about a new DB (I never really trusted Mongo and only used it to play with). In this case I don't see postgres as "new and unproven" but rather "proven and pushing the envelope" which is what excites me.