Why Should You Use MySQL? • Hacker News Board

Re: Why Should You Use MySQL?

#11

Post by AaronBBrown » Sun, Jan 27, 2013, 11:28 PM UTC

Yes...this.

Another thing that is often overlooked is tiered slaves in conjunction with logical replication for adding OLAP to an OLTP infrastructure. This allows you to have additional reporting data on slaves that is not present on the master and along with real-time replication, eliminating or simplifying nightly batch processing. This also allows you to keep a very small working set available on the master database with slaves that contain the full archive. In conjunction with BLACKHOLE tables, this can be very powerful.

Re: Why Should You Use MySQL?

#12

Post by camus » Sun, Jan 27, 2013, 11:28 PM UTC

yummyfajitas wrote: post #3

1 reason to use MySQL rather than Postgres: 1) Your legacy shared hosting site might provide MySQL and not Postgres. There are also 9 reasons to choose one of {Postgres, MySQL} over {Oracle, SQL Server}. Here is 1 reason to use Postgres: data integrity. "00/00/0000 00:00:00.0000" is not a real date, but MySQL will helpfully insert it into your table if you try to insert NULL into a non-null datetime field. (One examp…

1) is not even valid in my opinion , if the shared host doesnt provide at least postgre , it is not worth it.

The only reason to go with mysql is when one uses a CMS that is tied to mysql ( wordpress for instance or several ecommerce scripts).

Otherwise there is no need to stick to MYSQL.

Re: Why Should You Use MySQL?

#13

Post by bsg75 » Sun, Jan 27, 2013, 11:31 PM UTC

> You don’t need to hire a group of certified DBAs to run a MySQL database. An ordinary programmer can learn enough to maintain their database servers for most applications.

There is a reason why I, as someone whose experience in principally in data management, does not "write applications" - I might be able to write something that works, but it will likely lack security, stability, scalability. The same things happen with app developers, without an equivalent of database expertise, will make similar mistakes.

You may need a team of "certified" DBAs, but you need someone to guide the development of a stable foundation.

Re: Why Should You Use MySQL?

#14

Post by AaronBBrown » Sun, Jan 27, 2013, 11:33 PM UTC

toddh wrote: post #7

RDS as a scaling strategy is also a good reason.

RDS isn't really that great as a scaling strategy. It's only marginally easier to keep running than your own dedicated MySQL instances and it's far less flexible, particularly for disaster recovery since there is no way to do cross-region replication.

Re: Why Should You Use MySQL?

#15

Post by willlll » Sun, Jan 27, 2013, 11:35 PM UTC

camus wrote: post #12

yummyfajitas wrote: post #3

1 reason to use MySQL rather than Postgres: 1) Your legacy shared hosting site might provide MySQL and not Postgres. There are also 9 reasons to choose one of {Postgres, MySQL} over {Oracle, SQL Server}. Here is 1 reason to use Postgres: data integrity. "00/00/0000 00:00:00.0000" is not a real date, but MySQL will helpfully insert it into your table if you try to insert NULL into a non-null datetime field. (One examp…

1) is not even valid in my opinion , if the shared host doesnt provide at least postgre , it is not worth it. The only reason to go with mysql is when one uses a CMS that is tied to mysql ( wordpress for instance or several ecommerce scripts). Otherwise there is no need to stick to MYSQL.

That's not even a good reason. Pick a better CMS.

Re: Why Should You Use MySQL?

#16

Post by tveita » Sun, Jan 27, 2013, 11:36 PM UTC

These are all reasons why you'll do fine with MySQL if you're stuck with it, but they don't give a compelling reason to choose MySQL over e.g. PostgreSQL.

One thing I like about MySQL is the support available from third parties like Percona - I'll also recommend the book "High Performance MySQL", which gives some great details on performance tuning and query optimizing.

I'm not familiar with the offers for PostgreSQL - I'd like to hear what support services and books people with PostgreSQL experience would recommend.

Re: Why Should You Use MySQL?

#17

Post by taligent » Sun, Jan 27, 2013, 11:39 PM UTC

yummyfajitas wrote: post #3

1 reason to use MySQL rather than Postgres: 1) Your legacy shared hosting site might provide MySQL and not Postgres. There are also 9 reasons to choose one of {Postgres, MySQL} over {Oracle, SQL Server}. Here is 1 reason to use Postgres: data integrity. "00/00/0000 00:00:00.0000" is not a real date, but MySQL will helpfully insert it into your table if you try to insert NULL into a non-null datetime field. (One examp…

2) Clustering e.g. multi-master solution.

3) Decent monitoring.

4) Commercial support.

And your argument about data integrity is valid but in the real world moot. Most developers are using an ORM these days which abstract problems like these away.

Re: Why Should You Use MySQL?

#18

Post by rimantas » Sun, Jan 27, 2013, 11:39 PM UTC

yummyfajitas wrote: post #3

1 reason to use MySQL rather than Postgres: 1) Your legacy shared hosting site might provide MySQL and not Postgres. There are also 9 reasons to choose one of {Postgres, MySQL} over {Oracle, SQL Server}. Here is 1 reason to use Postgres: data integrity. "00/00/0000 00:00:00.0000" is not a real date, but MySQL will helpfully insert it into your table if you try to insert NULL into a non-null datetime field. (One examp…

And if you don't want this kind of helpfulness, check out http://dev.mysql.com/doc/refman/5.5/en/server-sql-mode.html

Re: Why Should You Use MySQL?

#19

Post by rosser » Sun, Jan 27, 2013, 11:42 PM UTC

tveita wrote: post #16

These are all reasons why you'll do fine with MySQL if you're stuck with it, but they don't give a compelling reason to choose MySQL over e.g. PostgreSQL. One thing I like about MySQL is the support available from third parties like Percona - I'll also recommend the book "High Performance MySQL", which gives some great details on performance tuning and query optimizing. I'm not familiar with the offers for PostgreSQL…

For support, peruse the list for your continent at:

http://www.postgresql.org/support/professional_support/

For books, among the most important is Greg Smith's "PostgreSQL 9.0 High Peformance", but really, just search Amazon for "PostgreSQL" and browse the titles until you find one that matches your needs.

Personally, I've been working with postgres for a decade now. Most of what I've needed, I've just gotten from searching a/o asking on the mailing lists.

Re: Why Should You Use MySQL?

#20

Post by AaronBBrown » Sun, Jan 27, 2013, 11:42 PM UTC

coderdude wrote: post #10

yummyfajitas wrote: post #3

1 reason to use MySQL rather than Postgres: 1) Your legacy shared hosting site might provide MySQL and not Postgres. There are also 9 reasons to choose one of {Postgres, MySQL} over {Oracle, SQL Server}. Here is 1 reason to use Postgres: data integrity. "00/00/0000 00:00:00.0000" is not a real date, but MySQL will helpfully insert it into your table if you try to insert NULL into a non-null datetime field. (One examp…

One thing that bugs me is MySQL will truncate a value if the column can't hold it all and will only issue a warning (by default?). Although in most instances I've already done the foot work of checking a value's length, it would be nice to be able to throw an exception when it occurs. Of course that could be the choice of my framework and not MySQL's fault.

  SET sql_mode = 'STRICT_ALL_TABLES';

http://dev.mysql.com/doc/refman/5.5/en/server-sql-mode.html#...

Yes, it's not default. Yes, it can be overridden. Yes, that bothers a lot of people.