When MariaDB first told publicly that they would relase '5.2' i strong recommended that they did not. The problem is that *generic clients* (clients that are supposed to support multiple server versions - what includes all GUI clients) will need to execute SELECT VERSION() to identify what features the server supports (EVENTS or not, LOAD DATA XML or not and so on). Further there actually was a MySQL 5.2 some years ago (it was continued as 6.0). So the version '5.2' is ambigious really. This is not a big deal as nobody takes the old MySQL 5.2 seriously (even though it is still on official MySQL FTP-mirrors). But such ambiguity should be avoided in the future - PLEASE! :-) The actual problem with MariaDB registering in WB can be solved by setting up the service as 'mysqlmaria52' in Windows (as far as I remember services can be 16 characters). -- Peter On Mon, Feb 21, 2011 at 13:32, Kazuhisa Ichikawa <kahzoo@gmail.com> wrote:
Just a thought, but wouldn't it be nice if MariaDB 5.2 provided a command line option (or a configuration variable) which makes it look like MySQL 5.1 to the client (by returning 5.1.something as its version) ?
2011/2/19 Vladislav Vaintroub <wlad@montyprogram.com>:
I researched it a little bit further.
So, the below bug can be worked around with
mysqld –install
Assuming you have my.ini in the installation directory, you’ll get service named MySQL, which will be using my.ini config file n the installation root.
With this configuration, WB does not crash, and you can point it to my.ini. And my.ini settings will *not* be shown in the WB configuration settings, as you say. For MariaDB 5.2 that is. For MariaDB 5.1 however, it works. My theory is that Workbench checks version prior presenting config file options. 5.2 is not a known version, hence config editor behavior is erratic. I cannot think of other explanation for this behavior , as my.ini files are identical in my tests, the only thing which is different here is the version string.
Vladislav.
PS. I don’t think Oracle Workbench folks would see this behavior as a bug btw, as they are not bound to support Maria.
From: maria-discuss-bounces+wlad=montyprogram.com@lists.launchpad.net [mailto:maria-discuss-bounces+wlad=montyprogram.com@lists.launchpad.net] On Behalf Of Vladislav Vaintroub Sent: Freitag, 18. Februar 2011 14:18 To: 'Jake Drew'; maria-discuss@lists.launchpad.net Subject: Re: [Maria-discuss] Installing MariaDB using MySQL Workbench on Windows
Jake, I tried to do instance setup on my machine using your description. Workbench brings a nicely designed popup “has encountered a bug, please report”, during “Management and OS” step. So I did, reported it here http://bugs.mysql.com/bug.php?id=60167
From: maria-discuss-bounces+wlad=montyprogram.com@lists.launchpad.net [mailto:maria-discuss-bounces+wlad=montyprogram.com@lists.launchpad.net] On Behalf Of Jake Drew Sent: Donnerstag, 17. Februar 2011 22:39 To: maria-discuss@lists.launchpad.net Subject: [Maria-discuss] Installing MariaDB using MySQL Workbench on Windows
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp