> >> > > So, had you taken the time to read the manual, you would have known
> >> > > this already.
> >> >
> >> > True, but if "engine substitution" is the default, than IMO, that's
> > wrong.
> >> >
> >> Why is it wrong? It is what the manual states. Maybe you think that
> >> not having stricT SQL mode set is wrong and that you should have to
> >> configure it to do other things.
> >>
> >> The manual states what is the default and tells you haw to change it.
> >> What is wrong about that?
> >
> > It's a silly default :-)
> >
> > IMO, "strict sql" should be the default as well. MySQL is slowly getting
> > more and more strict, which is a good thing. It's just strange that it
> > wasn't
> > strict when it started
>
> So noted. I'm sure the developers will give your opinion all due
> consideration when looking into whether to change established behavior.

Hmm, not too quick. Backwards compatibility is a good thing...

The MySQL crew and I disagree on some of those with regard to
major and minor releases and making things deprecated...

I must say I don't remember if the MySQL 5 (Windows) installer has
some kind of option whether you want "strict SQL" or not, that would
be nice.


--
Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, NexusDB, Oracle &
MS SQL Server
Upscene Productions
http://www.upscene.com
My thoughts:
http://blog.upscene.com/martijn/
Database development questions? Check the forum!
http://www.databasedevelopmentforum.com