Hi,
I think your client does not read the config file at all. Otherwise it wouldn't even start, because character-set-server is a server-only option, unknown for the client.
To find out where the client looks for configuration files, you can issue mysql --help command and search for
"Default options are read from the following files in the given order:"
Next line will contain the list of locations.
Hi Elena,
You are absolutely right! I copied my.ini from c:\webserver\MariaDB\data\my.ini and after deleting a few character-set-server options not recognized by the mysql utility, it worked!
I expected the mysql client utility would read the ini from the data directory (which is where the mariadb service expects to find my.ini to start the database server), but I guess it does not.
Damn, this is why I like MariaDB much more than MySQL. I had my issue resolved in a couple of minutes. Thank you guys, you rock! Feel free to close this bug.
Best regards,
Vasilis
Glad it worked for you, closing as suggested.
In regard to the datadir – I don't think the client is even theoretically capable of finding a config file there, on the simple reason that it's unaware of the datadir at all – it's a server's property, and it's configurable, so cannot be hard-coded in the client or calculated relatively to the basedir.
"don't think the client is even theoretically capable of finding a config file there"
There is a little known fact , or perhaps unknown to anyone except MSI installer author
MSI installation creates command prompt shortcut (start=>all programs=>MariaDB x.y=>Command Prompt(MariaDB x.y)). When started , not only PATH variable is set so it includes "bin" directory, but also MYSQL_HOME variable is set to datadir, so that client can find my.ini file.
Indeed, good to know
And one doesn't even have to use the special command prompt, just set MYSQL_HOME in the environment to get it work.