http://gabrito.com/post/mysql-and-not-null-is-not-good Anecdotes on Java, Ruby, Sysadmin, SEO, Design, and Management Thu, 04 Dec 2008 20:33:04 +0000 http://wordpress.org/?v=2.6.3 http://gabrito.com/post/mysql-and-not-null-is-not-good#comment-1090 When installing MySQL always set the sql-mode Sun, 28 May 2006 19:51:13 +0000 http://gabrito.com/post/23#comment-1090 [...] As I’ve described before, MySQL has some appalling out of the box settings which will thwart your attempts at good data integrity! They’ve clearly seen the light though and at least give you an option to achieve good data integrity through foreign keys in InnoDB and proper handling of non-nullable fields and invalid values through the servers sql-mode setting. What compounds the problem is that it seems MySQL may have different settings per platform. For example a friends 5.0.21 install on Windows XP had the sql-mode set with relatively strict settings whereas 5.0.18 on my Mac did not. If you’re configuring MySQL for a new greenfield project there are 2 things that you should absolutely always do in your my.cnf (or my.ini in Windows): [...] [...] As I’ve described before, MySQL has some appalling out of the box settings which will thwart your attempts at good data integrity! They’ve clearly seen the light though and at least give you an option to achieve good data integrity through foreign keys in InnoDB and proper handling of non-nullable fields and invalid values through the servers sql-mode setting. What compounds the problem is that it seems MySQL may have different settings per platform. For example a friends 5.0.21 install on Windows XP had the sql-mode set with relatively strict settings whereas 5.0.18 on my Mac did not. If you’re configuring MySQL for a new greenfield project there are 2 things that you should absolutely always do in your my.cnf (or my.ini in Windows): [...]

]]> http://gabrito.com/post/mysql-and-not-null-is-not-good#comment-14 Todd Huss’ blog » Blog Archive » The time has come to upgrade to MySQL 5 Fri, 13 Jan 2006 23:37:26 +0000 http://gabrito.com/post/23#comment-14 [...] We’ve finally hit the point at work where we’re ready to upgrade from MySQL 4.0 to 5. Data integrity has been a problem since I started at this job. Part of the reason is that MySQL 4.0 has an odd (to put it lightly) interpretation of not null and we still have a fair amount of legacy Perl code running the administrative portion of the site that lets bad data through. The lack of subselects for ad-hoc querying, aggregation functions, stored procedures, and triggers has also grown more irritating knowing that MySQL 5 has those features. [...] [...] We’ve finally hit the point at work where we’re ready to upgrade from MySQL 4.0 to 5. Data integrity has been a problem since I started at this job. Part of the reason is that MySQL 4.0 has an odd (to put it lightly) interpretation of not null and we still have a fair amount of legacy Perl code running the administrative portion of the site that lets bad data through. The lack of subselects for ad-hoc querying, aggregation functions, stored procedures, and triggers has also grown more irritating knowing that MySQL 5 has those features. [...]

]]>