I think users of postgresql are usually more experienced, care about features and complete polls than users of mysql who probably don't user foreign-key constraints.
Citation please. (I prefer Postgres, but your statement seems harsh.)
PostgreSQL is more popular than MySQL
31–40 of 51 posts
Re: PostgreSQL is more popular than MySQL
#32I think users of postgresql are usually more experienced, care about features and complete polls than users of mysql who probably don't user foreign-key constraints.
Citation please. (I prefer Postgres, but your statement seems harsh.)
I'm talking solely based on my experience, which has been much harsher than I wrote in my comment. I know in-person only 1 guy that likes postgresql and he had good reasons for it and experience with many rdbms. While everyone else is like: lol php+mysql for life (talking only people that I know in-person).
Nearly the same experience, but much better is online in my opinion.
Exercise: Go to reddit.com/r/postgresql and reddit.com/r/mysql and see if there is any difference in topics.
Re: PostgreSQL is more popular than MySQL
#33Other data points... StackOverflow questions - MySQL: 279,125 - PostgreSQL: 32,040 Github repository results - MySQL: 16,476 - PostgreSQL: 4,332
The question is what is your favorite. I use MySQL and Postgress. I use MySQL more, but I would say I prefer Postgress for features,so depends what definition of popular you are using (by usage, or by users personal favorite).
Re: PostgreSQL is more popular than MySQL
#34In this survey I learned that dBase/Clipper, as well as Access, are relational databases.
I actually liked working with XBase back in the 80s, but I don't miss not having foreign key constraints enforced, not having transactions, having long data values truncated, not being able to take a backup while running.
Early MySQL was too much like XBase for my taste, whereas PostgreSQL felt like a "real" database. I realize the InnoDB backend makes data integrity a bit more of a priority, but MySQL always felt like "worse is better", even if a bunch of "will code HTML for food" 90s internet crack heads helped make it ubiquitous. Windows is ubiquitous, and that doesn't mean much to me.
Re: PostgreSQL is more popular than MySQL
#35Earlier quoted context omitted.
I legitimately don't understand how Oracle remains so popular. I mean, I use it at work, but that is because this project dates back to the late 1980s(!) and decisions were made 20+ years ago. It doesn't even support a Boolean type(!), costs a ton (over 2x MS SQL, 4x Postgres), passwords are limited to 30 characters, up until 2007 passwords were case insensitive, error feedback is "basic," and the syntax is horrific.…
Mm, my understanding is that it's for a few reasons: - Oracle have good name recognition (no one ever fired for using Oracle), presumably an army of support people, well trained consultants, etc. - Postgres traditionally has not been as perforrmant, which makes it less useful for very large datasets. - Furthermore Oracle perf can usually be improved further by hinting properly, which is not possible in Postgres. Cert…
"Nobody ever got fired for buying Oracle" perhaps?
Re: PostgreSQL is more popular than MySQL
#36I think users of postgresql are usually more experienced, care about features and complete polls than users of mysql who probably don't user foreign-key constraints.
Citation please. (I prefer Postgres, but your statement seems harsh.)
It makes some sense to me. I always find it pretty painful writing anything but the most simple queries in MySQL - for starters, there's no CTEs, no windowing functions, and no table-valued functions, all of which I find invaluable - and the query optimizer (and performance in general) seems... not so hot.
As far as I can tell, the main reasons people use MySQL are 1) it's well-known, well-documented, free, and widely available; shared hosting, for example, is almost always MySQL and 2) replication. I often wonder if the inadequacies of MySQL are part of the reason for the success of NoSQL databases and general un-hipness of relational databases.
Re: PostgreSQL is more popular than MySQL
#37Earlier quoted context omitted.
Citation please. (I prefer Postgres, but your statement seems harsh.)
It makes some sense to me. I always find it pretty painful writing anything but the most simple queries in MySQL - for starters, there's no CTEs, no windowing functions, and no table-valued functions, all of which I find invaluable - and the query optimizer (and performance in general) seems... not so hot. As far as I can tell, the main reasons people use MySQL are 1) it's well-known, well-documented, free, and widel…
I used MySQL a lot at my last job (MS SQL Server now, which has its own ups and downs) and I examined using Postgres for some personal projects, and there's a few features that I used rather heavily in MySQL (partitioned tables and upsert are the really big ones) that Postgres doesn't have an out-of-the-box equivalent to. There's a lot of tradeoffs between the two, I think it's wrong to say one is better than the other without context.
Re: PostgreSQL is more popular than MySQL
#38Why are MySQL and MariaDB shown separately. For all intensive purposes they are the same.
I might have agreed with that when the two initially forked, however the gap continues to widen: https://mariadb.com/kb/en/mariadb/mariadb-vs-mysql-compatibi...
So far as liking one versus the other; they are the same. Nobody is going to say "I like MySQL over MariaDB because I have to change MarioDB options to make it work the same as MySQL".
Re: PostgreSQL is more popular than MySQL
#39Why are MySQL and MariaDB shown separately. For all intensive purposes they are the same.
I'm quite surprised that Percona Server didn't make an appearance in the list.
Re: PostgreSQL is more popular than MySQL
#40Earlier quoted context omitted.
It makes some sense to me. I always find it pretty painful writing anything but the most simple queries in MySQL - for starters, there's no CTEs, no windowing functions, and no table-valued functions, all of which I find invaluable - and the query optimizer (and performance in general) seems... not so hot. As far as I can tell, the main reasons people use MySQL are 1) it's well-known, well-documented, free, and widel…
I used MySQL a lot at my last job (MS SQL Server now, which has its own ups and downs) and I examined using Postgres for some personal projects, and there's a few features that I used rather heavily in MySQL (partitioned tables and upsert are the really big ones) that Postgres doesn't have an out-of-the-box equivalent to. There's a lot of tradeoffs between the two, I think it's wrong to say one is better than the oth…
Postgres does have partitioned tables, although the implementation is different from MySQL's. Upsert stands, though.
I don't disagree there's tradeoffs - I mentioned replication, for example, but it seems to me that MySQL is lacking a lot of features that other DBMS's provide and except for a few use cases, the fewer features unique (or better implemented) in MySQL doesn't make up for it.
Honestly I prefer SQL Server by leaps-and-bounds over the four I've used enough to be very familiar with - MySQL, MS SQL, Oracle, and Postgres - but I think Postgres has much more to offer to most users for most use cases than MySQL.