Bug #3651 long options wrongly accept "--option arg" whereas only --option=arg should
Submitted: 4 May 2004 17:03 Modified: 4 May 2004 21:50
Reporter: Guilhem Bichot Email Updates:
Status: Won't fix Impact on me:
None 
Category:MySQL Server: Command-line Clients Severity:S3 (Non-critical)
Version:4.0 OS:Linux (Linux at least)
Assigned to: Sergei Golubchik CPU Architecture:Any

[4 May 2004 17:03] Guilhem Bichot 
Description:
(didn't test 3.23).
Affects our clients and mysqld.
example with mysql:
mysql --database db
is accepted ("db" is considered as the argument of --database), whereas only mysql --database=db should, according to the manual.
Here is how it can cause problems:
[guilhem@gbichot2 mysql-4.0]$ mysql --database --nobeep
ERROR 1049 (): Unknown database '--nobeep'

How to repeat:
mysql --database --nobeep
[4 May 2004 21:50] Sergei Golubchik 
Unfortunately - as I don't like this behaviour either - it happend to be the way GNU getopt works. my_getopt is trying to be compatible.

$ man 3 getopt
...
 A long option may take a parameter, of the form --arg=param or --arg param.
...
$ tar --create --file --gzip .
$ ls
... --gzip ...
$