sadmysqluser

5 ms·

1. 1.▲
   by sadmysqluser 14y ago

   If you read pippy's statement carefully Also I have no idea what my users will do, and I'd rather have faulty data inserted than none at all. you'll see we're in agreement - PostgreSQL's design and feature set makes it clearly supe
2. 2.▲
   by sadmysqluser 14y ago

   You're mistaken if you think MySQL and PostgreSQL and the other databases are simply going to stand still during that time and you're also mistaken if you think applications which work with the SQL model will be abandoned before a better mo
3. 3.▲
   by sadmysqluser 14y ago

   Commercial support for MySQL is evolving in a similar way. Oracle, Percona, SkySQL and others offer it (emphasizing their particular value-added flavor).
4. 4.▲
   by sadmysqluser 14y ago

   Personally I prefer PostGreSQL over MySQL for a drop in replacement on Linux based systems. It’s far superior in many ways, and something you should consider if you’re able to. Personally if I were to start a new business or had a Linux ba
5. 5.▲
   by sadmysqluser 14y ago

   Somethings's up with your site. All I see are black boxes where your examples should be: http://imgur.com/N8vdzGX
6. 6.▲
   by sadmysqluser 14y ago

   If you would rather have faulty data than none when something's wrong with your application, then MySQL is your DB of choice.
7. 7.▲
   by sadmysqluser 14y ago

   I've never recommended MySQL for anything where the data is important, but I've had to help several businesses deal with existing installations. Here's a few teachable moments: One customer who ran MySQL on windows experienced data loss af
8. 8.▲
   by sadmysqluser 14y ago

   Ronald Bradford's http://www.slideshare.net/ronaldbradford/my-sql-idiosyncrasi... is worth reviewing for anyone who runs MySQL. I especially like how he explains SQL_MODE bit by bit and ends up recommending SQL_MODE =