Comments on: Why SQL_MODE is important http://ronaldbradford.com/blog/why-sql_mode-is-important-2011-06-01/ Expert times and information on MySQL Thu, 09 May 2013 15:50:26 +0000 hourly 1 http://wordpress.org/?v=3.0.4 By: Why SQL_MODE is essential if still ineffective « MySQL Expert | MySQL Performance | MySQL Consulting http://ronaldbradford.com/blog/why-sql_mode-is-important-2011-06-01/comment-page-1/#comment-14047 Why SQL_MODE is essential if still ineffective « MySQL Expert | MySQL Performance | MySQL Consulting Thu, 16 Feb 2012 19:00:53 +0000 http://ronaldbradford.com/blog/?p=3705#comment-14047 [...] Why SQL_MODE is important [...] [...] Why SQL_MODE is important [...]

]]> By: Henrik Ingo http://ronaldbradford.com/blog/why-sql_mode-is-important-2011-06-01/comment-page-1/#comment-12518 Henrik Ingo Mon, 06 Jun 2011 05:32:55 +0000 http://ronaldbradford.com/blog/?p=3705#comment-12518 Ronald, I think you are mixing two concepts here: data type and constraints. In your example it just happens that zero was the minimum value for the data range being stored. So using unsigned as data type also works as a constraint. But that's not the case in general - for instance what if your minimum value would have been one (1)? Ronald, I think you are mixing two concepts here: data type and constraints. In your example it just happens that zero was the minimum value for the data range being stored. So using unsigned as data type also works as a constraint. But that’s not the case in general – for instance what if your minimum value would have been one (1)?

]]> By: Ovais Tariq http://ronaldbradford.com/blog/why-sql_mode-is-important-2011-06-01/comment-page-1/#comment-12510 Ovais Tariq Fri, 03 Jun 2011 11:06:45 +0000 http://ronaldbradford.com/blog/?p=3705#comment-12510 Hi Ronald, I completely agree with you over the use of the SQL MODE, traditionally MySQL has been very forgiving and that stems from the fact that traditionally MyISAM (which is a non-transactional storage engine) is the default storage engine that is being used., and with MyISAM if a multi-row insert or update causes an error and you are using the strict SQL MODE then partial updates/inserts can happen if the error happens after the first row. Because MyISAM is not a transactional storage engine and there is no way it can rollback the updates/inserts. And it seemed better to avoid partial updates. So my recommendation is use InnoDB together with a strict SQL MODE, so that if there is any error that is encountered, then the changes can be rolled back and hence no partial update issue. Hi Ronald,

I completely agree with you over the use of the SQL MODE, traditionally MySQL has been very forgiving and that stems from the fact that traditionally MyISAM (which is a non-transactional storage engine) is the default storage engine that is being used., and with MyISAM if a multi-row insert or update causes an error and you are using the strict SQL MODE then partial updates/inserts can happen if the error happens after the first row. Because MyISAM is not a transactional storage engine and there is no way it can rollback the updates/inserts. And it seemed better to avoid partial updates.

So my recommendation is use InnoDB together with a strict SQL MODE, so that if there is any error that is encountered, then the changes can be rolled back and hence no partial update issue.

]]> By: Silvia http://ronaldbradford.com/blog/why-sql_mode-is-important-2011-06-01/comment-page-1/#comment-12503 Silvia Thu, 02 Jun 2011 12:27:20 +0000 http://ronaldbradford.com/blog/?p=3705#comment-12503 It's like the default MyISAM engine issue (until very recently). This is why using the out of the box configuration is never a good idea. It’s like the default MyISAM engine issue (until very recently). This is why using the out of the box configuration is never a good idea.

]]> By: Shlomi Noach http://ronaldbradford.com/blog/why-sql_mode-is-important-2011-06-01/comment-page-1/#comment-12502 Shlomi Noach Thu, 02 Jun 2011 05:01:51 +0000 http://ronaldbradford.com/blog/?p=3705#comment-12502 @Brian, Does that mean UNSIGNED only has half as much possible values? (Having limited a SIGNED integer?) @Brian,
Does that mean UNSIGNED only has half as much possible values? (Having limited a SIGNED integer?)

]]> By: Brian Aker http://ronaldbradford.com/blog/why-sql_mode-is-important-2011-06-01/comment-page-1/#comment-12500 Brian Aker Thu, 02 Jun 2011 02:44:58 +0000 http://ronaldbradford.com/blog/?p=3705#comment-12500 Hi! Drizzle does have UNSIGNED. We added it back in the beginning of the year so that we could gain some compatibility that we needed in a couple of places. We treat it has a constraint though, not as a type (which is somewhat hairsplitting, but it is useful to know). Cheers, -Brian Hi!

Drizzle does have UNSIGNED. We added it back in the beginning of the year so that we could gain some compatibility that we needed in a couple of places.

We treat it has a constraint though, not as a type (which is somewhat hairsplitting, but it is useful to know).

Cheers,
-Brian

]]> By: Ronald Bradford – 42SQL: Why SQL_MODE is important | Weez.com http://ronaldbradford.com/blog/why-sql_mode-is-important-2011-06-01/comment-page-1/#comment-12498 Ronald Bradford – 42SQL: Why SQL_MODE is important | Weez.com Wed, 01 Jun 2011 20:07:58 +0000 http://ronaldbradford.com/blog/?p=3705#comment-12498 [...] View full post on Planet Drizzle [...] [...] View full post on Planet Drizzle [...]

]]>