My preferred DBMS is Postgres, but I have to use MySQL at work. I can honestly say that moving to MySQL after Postgres is a serious downer. What happens when you want referential integrity alongside fulltext indexes? An ugly database.
MySQL vs PostgreSQL
11–20 of 27 posts
Re: MySQL vs PostgreSQL
#12I've read many MySQL vs Postgres articles/papers over the years. This one is the best. Not highly opinionated. "Just the facts" mostly. And in a good format.
Thanks for publishing!!!
oh yeah, go postgres!!! ;)
Re: MySQL vs PostgreSQL
#13OTOH I was thinking about moving my app from MySQL to SQLite. Did anyone else has gone through the same situation?
That is a bad idea I think — SQLite locks the database while inserting data, obviously this is bad for a big application. I don't think it was designed for web apps with possibly hundreds of queries a second.
Re: MySQL vs PostgreSQL
#14OTOH I was thinking about moving my app from MySQL to SQLite. Did anyone else has gone through the same situation?
That is a bad idea I think — SQLite locks the database while inserting data, obviously this is bad for a big application. I don't think it was designed for web apps with possibly hundreds of queries a second.
You are right. But "hundreds of queries a second" are fine if there're mostly _read_ queries.
Re: MySQL vs PostgreSQL
#15I've read many MySQL vs Postgres articles/papers over the years. This one is the best. Not highly opinionated. "Just the facts" mostly. And in a good format. Thanks for publishing!!! oh yeah, go postgres!!! ;)
Great comparison of the most recent features and versions. It's nice to see PostGres get some kudos in the speed department. And, it's nice to hear about the upcoming developments of the Falcon and Maria engines.
Re: MySQL vs PostgreSQL
#16OTOH I was thinking about moving my app from MySQL to SQLite. Did anyone else has gone through the same situation?
That is a bad idea I think — SQLite locks the database while inserting data, obviously this is bad for a big application. I don't think it was designed for web apps with possibly hundreds of queries a second.
Thank you, but what is the definition of a big application? FaceBook? what if you were building something along FogBugz and the like? or maybe even something like BaseCamp? would SQLite fit those types of applications?
Re: MySQL vs PostgreSQL
#17This is very useful (although I am not qualified to say if it's definitive or not). I chose PostgreSQL based on one single fact that I ONCE crashed a MySQL server with a query (about 4 years ago) and I've never crashed PostgreSQL. It's a flimsy reason tbh but it's all I had to go on. Having said all that I do really love PostgreSQL now after 4 years of using it (via SQLAlchemy).
I tend to chose PostgreSQL because of the query language. It is more comfortable to program in. As ORMs become more prevalent, things like query language start to become less relevant, but so do relational databases. I really don't care how my data is stored, as long as it's safe and performs well.
ORMs are a case of "good enough for most," however, I have seen ridiculously dramatic increases in performance when dealing with millions of DB rows by using SQL and stored procedures. By design, it's pretty much impossible for an ORM to ever reach such levels of performance since they need to be generic enough to work across various RDMS systems and so forth.
Re: MySQL vs PostgreSQL
#18I've read many MySQL vs Postgres articles/papers over the years. This one is the best. Not highly opinionated. "Just the facts" mostly. And in a good format. Thanks for publishing!!! oh yeah, go postgres!!! ;)
I agree on both counts. I love postgre, but it took me a long time to learn the real differences from MySQL, what situations it's better in, etc. Wish this was around a long time ago...
Re: MySQL vs PostgreSQL
#19I don't understand why MySQL has 9 different storage engines. Would someone mind quickly posting the benefits of that architecture as opposed to focusing on one 'storage engine' and making it really good?
Well, I pose to you this question: Would you rather have 1 type of car that the government makes that works pretty reliably and is a middle-ground car, or would you rather have a selection of cars to chose from; sports, truck, sedan, minivan, etc. ? Everyone has different needs. I use MySQL extensively for it's memory-based storage engine, MyISAM for quick & dirty non-escential data i/o, and InnoDB for when data need…
The flexibility is great, but only if grouped with consistency. No foreign keys on MyISAM but yes on InnoDB? Thanks but no, thanks.
Re: MySQL vs PostgreSQL
#20OTOH I was thinking about moving my app from MySQL to SQLite. Did anyone else has gone through the same situation?
That is a bad idea I think — SQLite locks the database while inserting data, obviously this is bad for a big application. I don't think it was designed for web apps with possibly hundreds of queries a second.
SQLite is a lot faster than than the 'real' RDBMSes on single queries - so this lock on writing is not that painful as it might seem. I think SQLite is really eating into that quick-and-dirty db segment occupied by MySQL - while PostgreSQL is still ahead in the standard-compliant-robust-and-lot's-of-features department.