On 2010/06/01 18:06, Uwe Dippel wrote: > On Tue, Jun 1, 2010 at 5:18 PM, Antti Harri <i...@openbsd.fi> wrote: > > > I wasn't aware either and I had some weird problems when I upgraded from 5.0 > > to 5.1. I recall they were mostly procedure/trigger related. > > Yep, that's what the mysql_upgrade corrected here, mostly. > > Still, maybe someone should complain upstream about this behaviour: > 100531 20:37:23 [ERROR] /usr/local/libexec/mysqld: unknown option '--skip-bdb' > 100531 20:37:23 [ERROR] Aborting > ? > > A number of people have been bitten (lucky, for me, so to say) and had > their application aborted. > What, actually, is wrong to abort a configuration setting > # why not? > this is totally nonsense > # it really is! > especially, when 'this is totally nonsense' is a deprecated, earlier > valid, setting? > > I for preferred any message of an invalid parameter in the log file, > instead of aborting.
If it stops mysql from running, people will take notice. Many people will miss it if it's just in the log.
