From: Reindl Harald
Date: November 18 2012 11:11pm
Subject: Re: Why configuration directives are all case sensitive?
List-Archive: http://lists.mysql.com/mysql/228650
Message-Id: <50A96B14.7000501@thelounge.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature";
boundary="------------enigC72AEA30016FBF6F0C6FB982"
--------------enigC72AEA30016FBF6F0C6FB982
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Am 18.11.2012 23:59, schrieb Tianyin Xu:
> Hi,
>=20
> I'm just curious why MySQL parses its configuration directives (i.e., t=
he
> ones in my.cnf) in a case sensitive way?
>=20
> For example, Having "Port=3D3309", will receive "unknown variable 'Port=
=3D3309".
>=20
> I guess there must be some concern for this. Could anyone tell me why?
because every useable OS on this world is case-sensitive?
windows and partly MacOSX are the only OS on this world which
are not case-senstivie even for filenames and both are NOT
useable for servers at all
because "A" is binary not the same as "a"
because computers are working with binary data
because "a.txt" is not the same file as "A.txt"
because it is useless overhead to translate every input
because if you maintain a server you should have a working keyboard
because a configuration should be clear and not a guess what you mean
because if this is a problem for you maybe you have the wrong job
--------------enigC72AEA30016FBF6F0C6FB982
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/
iEYEARECAAYFAlCpaxQACgkQhmBjz394AnmlfACgnXnZbyF1cENSkEKZBrWCxLlq
U5wAn3ckNBWrm0L2cKZ9rhXDlOhQGODC
=TcIv
-----END PGP SIGNATURE-----
--------------enigC72AEA30016FBF6F0C6FB982--