![[TEST] Document Foundation Community](https://communitytest.documentfoundation.org/images/discourse-logo-sketch.png){kind=logo}
Hi 
Just thought a few people here might be interested in the new release of the drop-in replacement for MySql. It's especially good for those wanting to move away from Oracle products.
Regards from
Tom
But if you should change your mind, you might find it difficult to go back to MySQL. I had to re-install Ubuntu 12.04 LST to remove all of the MariaDB files. Something similar happened when I tried MariaDB a few years ago.
--Dan 
Hi
Thanks Dan. That sounds like a bit of a nightmare. I tend to prefer testing new things on a spare machine or on a spare partition but it's not always possible.
Apparently it also doesn't work on Macs although i'm entirely certain how far that goes. For example could Base as a front-end on a Mac read MariaDb as a back-end on a Debian server. Presumably it does but i don't know of anyone that has tried it.
Regards from
Tom
There is development work on a mysql/mariadb connector that Alex discovered requiring some changes in how the connecter is built. When working with the leading edge source code, I had to install MariaDB. Then I was informed that I needed to work with the 4.0 source code. That is when I had to re-install Ubuntu. But after that, I was able to build two mysql-connector-ooo.oxt: x86 for 32 bit AND x86-64 for 64 bit. As soon as I can finish everything within these files, I will upload them to the Extension section of the LO website. The working parts of these files work, but the documentation part is not what it should be yet.
--Dan
Hi Tom,
Apparently it also doesn't work on Macs although i'm entirely certain how far that goes. For example could Base as a front-end on a Mac read MariaDb as a back-end on a Debian server. Presumably it does but i don't know of anyone that has tried it.
Last time I looked, the mariadb server and client programs and libraries were only available via the ports installation system. This is a no go area for me on my OSX server, which is the machine I was using to build LO and the native mysql connector. The ports system on my Macbook screwed up the LO build by installing libraries that conflict with the ones used by the LO build process, so I stopped using my Macbook for building LO ages ago.
As far as I know, there are no pre-compiled MariaDB binaries for OSX.
Irrespective of the above, the changes being made in the mysql connector code should allow the connector to be built on all platforms where LO can be built, even if libmariadb is not already present. If the builder wants to use a system-present libmariadb, then there is also a compile time option to enable that. Otherwise, the aim is for the libmariadb source code to be downloaded at compile time. This currently works on Linux (from my build log on a 32bit OS), but I am still awaiting the results of test compilations on my OSX server.
Alex
Hi Alex,
A day or two ago I saw a MySQL-Native-Connector alpha version listed under
base extensions. Would be super to be able to try it out. Is there a way
to get involved in some testing?
Regards
H. S.
Dan,
I don't know where I read this warning, in this forum or some other, but there should be a warning to users who convert to Mariadb from MySQL. Yes, they can convert to Mariadb, but they may not be able to go back to MySQL once they used Mariadb on the database. I have not yet made that transition, so I have no direct experience with this and cannot corroborate it. If it is true, then a warning about this should be included with LO documentation referring to using Mariadb.
Girvin Herr
Dan Lewis wrote:
I agree. That will go into the chapter on using Base to connect to various data sources. I think that was originally scheduled to be chapter 8 or 9, but I think this chapter should be moved up to chapter 5.
Personal experience: I used synaptic to completely remove mariadb including the config files. Then when I tried to reinstall MySQL, synaptic insisted on installing a mariadb file instead of the mysql file. So, I reinstalled Ubuntu 12.04. Now I have MySQL back.
--Dan
Dan,
That is another issue. It is good that you were able to get MySQL back when you needed it. I think what I read was that Mariadb changed the database itself somehow, making it incompatible with MySQL. Thus, all the work done on it with Mariadb was lost from the last MySQL-compatible database backup. That is scary - lost data.
I just went searching again for where I read this caveat and came up with this posting by "ppr:kut" to LinuxQuestions.org on 1-31-13:
"I'm not sure what problems you imagine, but I'm not aware of any
issues. You wouldn't be able to switch easily from MariaDB back to
MySQL once you start using MariaDB specific features, but that's
clear from the start."
You can find this message and others on:
Now that I read it again, it sounds like they might be talking about Mariadb user features, not database compatibility. Kind of like someone who moves from msoffice to LO can't go back because they like the LO features. I would like to know if anyone has tried to go back to MySQL from using Mariadb and how *physically* successful it was.
Sorry about the confusion.
Girvin
Dan Lewis wrote:
Dan,
That is another issue. It is good that you were able to get MySQL back when you needed it. I think what I read was that Mariadb changed the database itself somehow, making it incompatible with MySQL. Thus, all the work done on it with Mariadb was lost from the last MySQL-compatible database backup. That is scary - lost data.I just went searching again for where I read this caveat and came up with this posting by "ppr:kut" to LinuxQuestions.org on 1-31-13:
"I'm not sure what problems you imagine, but I'm not aware of any
issues. You wouldn't be able to switch easily from MariaDB back to
MySQL once you start using MariaDB specific features, but that's
clear from the start."You can find this message and others on:
Now that I read it again, it sounds like they might be talking about Mariadb user features, not database compatibility. Kind of like someone who moves from msoffice to LO can't go back because they like the LO features. I would like to know if anyone has tried to go back to MySQL from using Mariadb and how *physically* successful it was.
Sorry about the confusion.
Girvin
Girvin, Dan
I once "updated" from MariaDB 5.5.x to MySQL 5.5.y then to MariaDB 5.5.y. I use MariaDB via localhost and found that the permissions are different. MariaDB default allows apps like MySQL Workbench to do bulk data inserts from files while MySQL does not. With MySQL I had to use the CLI version to do the inserts. I was unable to set the permissions in MySQL to allow MySQL Workbench to do bulk data inserts.
I am using Linux Mint Maya / 13. 64 bit. I have not yet tried the MySQL Connector and Base (LO 4.0.0.3). This might be an issue between the two forks.
Jay
Jay Lozier wrote:
Dan,
That is another issue. It is good that you were able to get MySQL back when you needed it. I think what I read was that Mariadb changed the database itself somehow, making it incompatible with MySQL. Thus, all the work done on it with Mariadb was lost from the last MySQL-compatible database backup. That is scary - lost data.I just went searching again for where I read this caveat and came up with this posting by "ppr:kut" to LinuxQuestions.org on 1-31-13:
"I'm not sure what problems you imagine, but I'm not aware of any
issues. You wouldn't be able to switch easily from MariaDB back to
MySQL once you start using MariaDB specific features, but that's
clear from the start."You can find this message and others on:
Now that I read it again, it sounds like they might be talking about Mariadb user features, not database compatibility. Kind of like someone who moves from msoffice to LO can't go back because they like the LO features. I would like to know if anyone has tried to go back to MySQL from using Mariadb and how *physically* successful it was.
Sorry about the confusion.
GirvinGirvin, Dan
I once "updated" from MariaDB 5.5.x to MySQL 5.5.y then to MariaDB 5.5.y. I use MariaDB via localhost and found that the permissions are different. MariaDB default allows apps like MySQL Workbench to do bulk data inserts from files while MySQL does not. With MySQL I had to use the CLI version to do the inserts. I was unable to set the permissions in MySQL to allow MySQL Workbench to do bulk data inserts.
I am using Linux Mint Maya / 13. 64 bit. I have not yet tried the MySQL Connector and Base (LO 4.0.0.3). This might be an issue between the two forks.
Jay
Jay,
Thanks for the information. I will file it away for the time I migrate to mariadb. So, let me get this straight - the mariadb server allows the MySQL apps to work better than with the MySQL server?! That is amusing.
For the record, I am using Slackware 12.2 32-bit and the mysql-connector-java with LO 3.6.4.3.
Thanks again.
Girvin
Bulk data inserts: Are you using this to append data to a table? (Add the data to a table that already contains data) I am not sure I understand.
I understand importing databases and their data as well as exporting them. Somehow I do not think that you were talking about importing databases or exporting them.
--Dan
I remember seeing (MySQL website?) where the change was made by MySQL to not allow this by default for security reasons while MariaDB maintained the old permissions. What is puzzling to me is that many who use MySQL or MariaDB via localhost are doing development or off-line database work and are not using remote access. I understand requiring tighter permissions if the database can be manipulated remotely to avoid major problems.
What was odd, I could issue TRUNCATE database but INSERT LOCAL FILE 'sdf.csv' etc would fail. I would think the opposite would be preferable.
Dan
I am importing data into an empty or truncated database. I am not appending data. I am using INSERT DATA LOCAL FILE etc. for the import.
Jay Lozier wrote:
Jay Lozier wrote:
Dan,
That is another issue. It is good that you were able to get MySQL back when you needed it. I think what I read was that Mariadb changed the database itself somehow, making it incompatible with MySQL. Thus, all the work done on it with Mariadb was lost from the last MySQL-compatible database backup. That is scary - lost data.I just went searching again for where I read this caveat and came up with this posting by "ppr:kut" to LinuxQuestions.org on 1-31-13:
"I'm not sure what problems you imagine, but I'm not aware of any
issues. You wouldn't be able to switch easily from MariaDB back to
MySQL once you start using MariaDB specific features, but that's
clear from the start."You can find this message and others on:
Now that I read it again, it sounds like they might be talking about Mariadb user features, not database compatibility. Kind of like someone who moves from msoffice to LO can't go back because they like the LO features. I would like to know if anyone has tried to go back to MySQL from using Mariadb and how *physically* successful it was.
Sorry about the confusion.
GirvinGirvin, Dan
I once "updated" from MariaDB 5.5.x to MySQL 5.5.y then to MariaDB 5.5.y. I use MariaDB via localhost and found that the permissions are different. MariaDB default allows apps like MySQL Workbench to do bulk data inserts from files while MySQL does not. With MySQL I had to use the CLI version to do the inserts. I was unable to set the permissions in MySQL to allow MySQL Workbench to do bulk data inserts.
I am using Linux Mint Maya / 13. 64 bit. I have not yet tried the MySQL Connector and Base (LO 4.0.0.3). This might be an issue between the two forks.
Jay
Jay,
Thanks for the information. I will file it away for the time I migrate to mariadb. So, let me get this straight - the mariadb server allows the MySQL apps to work better than with the MySQL server?! That is amusing.
For the record, I am using Slackware 12.2 32-bit and the mysql-connector-java with LO 3.6.4.3.
Thanks again.
GirvinI remember seeing (MySQL website?) where the change was made by MySQL to not allow this by default for security reasons while MariaDB maintained the old permissions. What is puzzling to me is that many who use MySQL or MariaDB via localhost are doing development or off-line database work and are not using remote access. I understand requiring tighter permissions if the database can be manipulated remotely to avoid major problems.
What was odd, I could issue TRUNCATE database but INSERT LOCAL FILE 'sdf.csv' etc would fail. I would think the opposite would be preferable.
I have been noticing how paranoid MySQL has been getting. That paranoia has a place, but for those of us who have local-only databases on a firewalled LAN, it would be nice to ease up on that paranoia and get more functionality. Now I hear that MySQL 5.5+ no longer uses localhost as the older versions did. It virtually takes over localhost bind functionality, all in the name of greater security. Good grief! I will find out soon. I am in the process of upgrading to Slackware 14.0 which comes with MySQL 5.5.
Girvin
I base my system upgrades (whichever 'buntu I decide to use) based on the MariaDB releases. I find the MySQL paranoia aggravating. It is almost as if Oracle is trying to break the community edition of MySQL while forgetting there are couple of very good forks available.
I do not think it is any more paranoid than usual. To get remote access to the server, one line of its configuration file (my.cnf) had to be altered for 5.1. Version 5.5 requires one line to be commented out using a #. So, I really don't understand what you mean by localhost bind functionality.
I have been using 5.5 since I installed Ubutu 12.04 late last spring or early summer without any problems other than connecting to the server remotely. But I may not have been using all the functionalities that you use. I am a little new to MySQL as it is. (I did have 5.1 running before I installed Ubuntu 12.04 though.)
I'm not sure I understand either what the "added" security measures are that bother you.
--Dan
Jay Lozier wrote:
Jay Lozier wrote:
<Let's do some snipping here....>
I have been noticing how paranoid MySQL has been getting. That paranoia has a place, but for those of us who have local-only databases on a firewalled LAN, it would be nice to ease up on that paranoia and get more functionality. Now I hear that MySQL 5.5+ no longer uses localhost as the older versions did. It virtually takes over localhost bind functionality, all in the name of greater security. Good grief! I will find out soon. I am in the process of upgrading to Slackware 14.0 which comes with MySQL 5.5.
GirvinI base my system upgrades (whichever 'buntu I decide to use) based on the MariaDB releases. I find the MySQL paranoia aggravating. It is almost as if Oracle is trying to break the community edition of MySQL while forgetting there are couple of very good forks available.
I am keeping an eye on this. Slackware is very pro open source. There are many software packages that Slackware does not bundle due to the Open Source pedigree being tainted. With MySQL going the way it is, I would not be surprised if some day in the near future, Slackware will change to Mariadb.
I generally update when I start having obsolescence problems that would be difficult to resolve. Right now, I am even getting complaints from ebay about my old Firefox, but upgrading it would require major core library changes and I am not willing to do that. Also, my current Slackware, 12.2, is now at the bottom of the security updates list. Soon it will no longer be supported. So, it is time.
Girvin