On 04/25/2012 05:52 PM, Andrés Tello wrote:
> Reads interesting, but...
> Why would you need that?
> I mean... If I run several databases in the same hardware, I use completely
> diferent paths for evertying, so I can have atomic, clean and specific
> files for each instance/version of the database....
Thanks for your opinion.
You're right, it doesn't make too much sense regarding system-wide
configuration files, such as /etc/my.cnf. A real use case I see is when
we speak about users' config files, like ~/.my.cnf.
Let's say we have two different MySQL versions on one hardware, then
it's possible we'll need a bit different options for each instance.
MySQL unfortunately doesn't distinguish between user-specific (usually
called rc files) and system-wide config files. Trying to have the patch
simple, I applied the feature to all config files (which was not necessary).
The attached patch now is a bit more complicated, but restricts the
feature only for config files in user's home directory. I believe this
makes more sense, than the original one.
Any comments welcome again.
Attachment: [text/x-patch] mysql-homeversionedcnf.patch