[Maria-discuss] Installing MariaDB using MySQL Workbench on Windows
Hello everyone,
I am trying to install MariaDB locally on a Windows XP desktop machine for testing purposes. We have a server coming (eventually), but I would like to get started in the meantime. There does not seem to be much information on installing and configuring MariaDB on Windows for use with the MySQL Workbench.
*Here are the steps I have taken so far:*
*Installed MariaDB on windows:*
1. Downloaded and ran MariaDB-5.2.4-win32-alt.exe
*Created MariaDB my.ini configuration file*
2. Copied C:\Program Files\MariaDB 5.2.4\my-large.ini 3. Pasted to C:\Program Files\MariaDB 5.2.4*my.ini* with no modifications ** *Created a Windows Service for MariaDB named MySQL and start that service on Windows:*
4. Start > Run > cmd.exe (open a command prompt) 5. cd C:\Program Files\MariaDB 5.2.4\bin 6. mysqld.exe --install MariaDB --defaults-file="C:\Program Files\MariaDB 5.2.4\my.ini" (got message "service was installed successfully", also see service listed in the "Services" window. 7. net start MariaDB (Service shows as started in "Services" window)
*Installed MySQL Workbench:*
8. Downloaded and ran mysql-workbench-gpl-5.2.31a-win32.msi
*Set up MariaDB Server on MySQL Workbench:*
9. Start MySQL Workbench and select "Create New Server Instance" 10. Made sure "Path to configuration file" under "Windows Management" pointed to: C:\Program Files\MariaDB 5.2.4\my.ini 11. Named the new server instance "MariaDB" 12. Double clicked the new server instance "MariaDB" after it was created.
*Got what appear to be success messages:* 2011-02-17 15:23:47 - Workbench will use cmd shell commands to start/stop this instance 2011-02-17 15:23:47 - Status check of service 'MariaDB' returned running 2011-02-17 15:23:48 - Server is running 2011-02-17 15:34:10 - Status check of service 'MariaDB' returned running
*Questions:*
1. Is there anything else I should do to configure MariaDB for use under Windows? 2. Almost all tabs under the "Configuration" section are blank in MySQL Workbench for the ner server instance MariaDB. This was not the case when I was running MySQL 5.1.53 on Windows. Is this normal? If not, can it be resolved?
Thanks!
Jake Drew
Hi!
On 18 Feb 2011, at 05:38, Jake Drew wrote:
1. Is there anything else I should do to configure MariaDB for use under Windows?
You had MariaDB configured to run and operate in a Microsoft Windows environment the moment you hit #7.
2. Almost all tabs under the "Configuration" section are blank in MySQL Workbench for the ner server instance MariaDB. This was not the case when I was running MySQL 5.1.53 on Windows. Is this normal? If not, can it be resolved?
Can you take a screenshot? I've tested this on the Mac version of Workbench and it just works as advertised (I do not have a Windows VM handy to repeat it in Microsoft Windows)
If there is a bug in Workbench, the best place to report it is http://bugs.mysql.com because Workbench is a product that Oracle makes
You do not need Workbench to make MariaDB run. If you want another alternative in Windows, I suggest using SQLYog - http://www.webyog.com/en/
cheers, -c -- Colin Charles, http://bytebot.net/blog/ | twitter: @bytebot | skype: colincharles MariaDB: Community developed. Feature enhanced. Backward compatible. Download it at: http://www.mariadb.org/ Open MariaDB/MySQL documentation at the Knowledgebase: http://kb.askmonty.org/
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
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
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
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
participants (5)
-
Colin Charles -
Jake Drew -
Kazuhisa Ichikawa -
Peter Laursen -
Vladislav Vaintroub