Justin, I appreciate your opinion, and if MySQL on Windows would not support multiple versions running on the same machine, I would agree.
But since we (and/or generations of programmers before me) chose to support multiple version of MySQL coexisting on the same machine, and I did not want to break it, I see no real alternative. From: Justin Swanhart [mailto:[email protected]] Sent: Freitag, 27. September 2013 19:54 To: Vladislav Vaintroub Cc: Peter Laursen; Maria Developers; Maria Discuss Subject: Re: [Maria-discuss] [Maria-developers] MySQL bug affects mariaDB Please ignore wrong block quote here - stupid mail on iPhone won't paste without it You know, windows does have easy ways to change the path and add variables to the environment without forcing shell invocation. It is just that in the case of VS you might cross-compile or choose to compile with Vs2008 or vs2012 as they can be installed simultaneously. I think if you are creating a service (in windows parlance) the client should know how to connect to the service sans hoops. Just my opinion... VS is not the way most windows programs do things and you should not violate the principal if least surprise. --Justin On Sep 27, 2013, at 1:06 PM, "Vladislav Vaintroub" <[email protected]> wrote: The command line clients are not services, and they are not started with --defaults-file, this is correct. But 1.We install shortcut to mysql client and shortcut does have --defaults-file , and the default-file points to the right place, i.e whenever you installed the mysql server instance On my machine (I used the default x64 installation), MySQL client shortcut is this C:\Windows\System32\cmd.exe /k " "C:\Program Files\MariaDB 5.5\bin\mysql.exe" "--defaults-file=C:\Program Files\MariaDB 5.5\data\my.ini" -uroot -p"” 2. Out installation also provides another shortcut – called Command Prompt( MariaDB …) It could be used to call arbitrary client utilities, mysqladmin or somesuch .It uses yet another, less known, trick to force client utilities to look for correct my.ini - it sets environment variable MYSQL_HOME to point to the the datadir ( Besides, it also sets PATH to include “bin” directory, so that calling mysqladmin or mysql would not result in “path not found”) The inspiration for this shortcut was a very similar feature of Visual Studio , the “Visual Studio 20xx Command Line”. The summary of my.ini client-side support is that : If you install with MSI, installer will create shortcuts that help client utilities to find correct my.ini . You can have multiple versions of the MariaDB installed, and the shortcuts will still work correctly – every version specific shortcut would point to version-specific my.ini Thus, I’d argue that this bug does not affect MariaDB. From: Maria-developers [mailto:maria-developers-bounces+wlad=montyprogram....@lists.launchpad.net] On Behalf Of Peter Laursen Sent: Freitag, 27. September 2013 10:06 To: Maria Developers; Maria Discuss Subject: [Maria-developers] MySQL bug affects mariaDB I think the 'mysql' client with MariaDB has a similar problem as it has with MySQL - refer? <http://bugs.mysql.com/bug.php?id=70443> http://bugs.mysql.com/bug.php?id=70443 MariaDB installer installs my.ini to /datadir - what with MariaDB is a subfolder to /basedir. The server will look for it correctly as the registry key defining the service has a --default-file specification. But the command line clients don't read the registry key. @Wlad? -- Peter -- Webyog _______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
