Comments on: But I DO want MySQL to say "ERROR"!

By: Those oversized, undersized variables defaults | code.openark.org

Those oversized, undersized variables defaults | code.openark.org — Wed, 09 Jun 2010 04:35:12 +0000

[...] to solve otherwise difficult problems. And in most cases, 1024 was just too low, resulting in silent (Argh!) truncating of the result, thus returning incorrect results. It is interesting to learn that [...]

By: Pythian Group: Log Buffer #183, a Carnival of the Vanities for DBAs | Weez.com

Sat, 20 Mar 2010 20:09:10 +0000

[...] Are you interested in MySQL Clustering? I am. Andew Morgan has a new post introducing a tutorial to Build MySQL Cluster 7.1 from source – including MySQL Cluster Connector for Java. With Alex Fatkulin maybe running into an as yet possibly, sort of , kinda non-discovered bug, it’s only fair we also get some vision into the dark side on the MySQL front. Shlomi Noach states But I DO want MySQL to say “ERROR”!. [...]

By: Log Buffer #183, a Carnival of the Vanities for DBAs | The Pythian Blog

Log Buffer #183, a Carnival of the Vanities for DBAs | The Pythian Blog — Fri, 19 Mar 2010 20:08:35 +0000

By: shlomi

shlomi — Thu, 18 Mar 2010 18:58:28 +0000

@Shatnanu

Weehee! Material for more posts!

By: Shatnanu Oak

Shatnanu Oak — Wed, 17 Mar 2010 09:07:23 +0000

The worst thing about mysql is that there are times when it does not think it necessary to throw a warning (bug id: 43930).
For e.g.

mysql> CREATE TABLE `table1` (`number` int(20) DEFAULT NULL) ENGINE=MyISAM;
Query OK, 0 rows affected (0.02 sec)

mysql> insert into table1 values ('19.54');
Query OK, 1 row affected (0.00 sec)

mysql> select * from table1;
+--------+
| number |
+--------+
| 20 |
+--------+
1 row in set (0.04 sec)

Or while MySQL starts even with Fatal Innodb errors? (bug id: 19027) There seems to be no way to log warnings on import. (bug id: 8684) You will need to write another post for the bugs (id: 29898) where DATE() function returns inconsistent results.

By: shlomi

shlomi — Sat, 13 Mar 2010 09:46:07 +0000

Ouch! Have just been trolled.
Since two days passed with no comment back from Gurjeet, I'm editting his message to add a "troll alert" or something.

By: Roland Bouman

Roland Bouman — Sat, 13 Mar 2010 07:59:18 +0000

Feeding time is over trolls, let's get back on-topic.

By: Bill Karwin

Bill Karwin — Sat, 13 Mar 2010 04:51:49 +0000

@Gurjeet: Are you the same Gurjeet Singh who works for EnterpriseDB -- the commercial vendor of PostgreSQL? It would be good form to disclose that fact when you diss the competition.

By: shlomi

shlomi — Sat, 13 Mar 2010 04:47:01 +0000

@Gurjeet,

A bit far fetched in th context of this post. There are plenty of reasons to use MySQL, and very large companies run very popular products on MySQL, successfully. Seems like something's going right?

I think the web if full of database wars; but eventually, both MySQL and Postgresql (as example) are *good* database systems, and both have their pros and cons.
I think saying "there's no reason to use MySQL, and PostgreSQL is far better" is not too serious.

By: Gurjeet Singh

Gurjeet Singh — Sat, 13 Mar 2010 00:19:07 +0000

If you are serious about your data, use something mature than MySQL. I don't see a reason why one would run MySQL instead of a more SQL compliant DB. There are quite a few out there, but my personal favorite is Postgres.

Added by shlomi, two days later:
Gurjeet, you are most welcome in this blog. I hope you find it interesting and would like you to visit often. However, this comment does take the form of troll-speech. Since you work at EnterpriseDB, you cannot be completely naive or innocent.
Let me know if you want this comment to be altogether removed.