- discuss - lists.mariadb.org

[Maria-discuss] FYI: askmonty.org/buildbot is moving to buildbot.askmonty.org/buildbot
by Daniel Bartholomew 04 Feb '10

04 Feb '10

All, This is an FYI for everyone that uses our buildbot web interface: Due to an upcoming server move I am in the process of moving our buildbot web interface from http://askmonty.org/buildbot to http://buildbot.askmonty.org/buildbot Both of the above currently work (and point at the same data), but as of Friday 5 Feb 2010 at approx 09:00 US Eastern time, http://askmonty.org/buildbot will turn into a redirect. The redirect will handle all of your old bookmarks (i.e. they should still work), but I thought I should at least let everyone know so that you aren't surprised by the move. I've already updated all of the links I could find on the askmonty.org wiki. And if you are wondering why I kept the /buildbot subdirectory in place on the new subdomain, well, it was easier and safer to keep it in place, so I did. If you connect directly to http://buildbot.askmonty.org you will automatically be redirected to the /buildbot subdir. Thanks! -- Daniel Bartholomew Monty Program - http://askmonty.org

1 0

[Maria-discuss] Replication and auto-increment
by Brian Evans 29 Jan '10

29 Jan '10

I was reading over the replication discussion on maria-developers I thought I'd share some thoughts that are not so technical as I do not understand the back end that well. Our system is currently a master-master WAN replication setup, each writing to a different DB with an offline process to do copies. Our databases extensively uses auto-increments on tables (more than necessary, but that's another story). Would future developments allow synchronous replication to occur on a single database when the WAN link has a single point of failure(SPoF)? How might an auto-increment system handle such a failure? This SPoF is our network link that can be a transient problem out of our control. Both sides may need to keep inserting data during this transient issue. This is usually not an issue 99% of the time, but it's better to prepare for downtime than trying to fix data errors in that 1%.

5 6

[Maria-discuss] MariaDB Twitter account
by Colin Charles 21 Dec '09

21 Dec '09

Hi! Does anyone know who runs the MariaDB twitter account? We'd like to get a hold of the login details, so that we can become more relevant on Twitter - i.e. start following people, answering questions, etc. If I don't get a response within 48 hours of this message, I'll contact Twitter to see if we can maybe get the account by them reassigning it to us. Cheers, -c -- Colin Charles, http://bytebot.net/blog/ "First they ignore you, then they laugh at you, then they fight you, then you win." -- Mohandas Gandhi

2 1

[Maria-discuss] Binding to network addresses
by Viljo Hakala 01 Dec '09

01 Dec '09

I am not sure whether this has been discussed. MySQL either binds to all network interfaces/addresses or to only single specified network address. Wouldn't this limitation be nice to have fixed in MariaDB, say I want to bind to 127.0.0.1 and a VIP network address, maybe management network address, but not to all network addresses on a server?

2 2

[Maria-discuss] Default Database Engine
by Richard Dunn 30 Nov '09

30 Nov '09

I have compiled and installed mariadb-5.1.39 on Mac OS X 10.6.2 and installed a 64-bit binary on CentOS 5. In both cases, MyISAM is still the default database engine. I would have expected it to be Maria. Did I miss something? Thanks, Richard

4 5

[Maria-discuss] [Kristian Nielsen] [Maria-developers] FOSDEM 2010
by Kristian Nielsen 11 Nov '09

11 Nov '09

It occured to me that this might be better to send to -discuss to get a wider audience. Sorry if you receive this twice. - Kristian.

1 0

[Maria-discuss] Additional promise to the MCA
by Henrik Ingo 09 Oct '09

09 Oct '09

Hi all As Monty blogged some time ago http://monty-says.blogspot.com/2009/08/thoughts-about-dual-licensing-open.h… ...we want to add a promise to our MariaDB contributors signing the MCA, that we will not use their contributions to restrict other licensees ability to contribute to Open Source. This text has now been approved by a lawyer. The question is, is it understandable? ********************************** Additional promise to contributions under the Monty Program Contributor Agreement Monty Program Ab promises to each contributor assigning rights under the Monty Program Ab Contributor Agreement, that when licensing 'products' (software), that include a contribution, to other 3rd parties, the license will be either i) an Open Source license (www.opensource.org), or ii) another license, in which case: * the other license will NOT restrict the licensee from making his own modifications to the product, including adding other suitably licensed code or other 'materials' from other sources (such as code available under suitable Open Source licenses) * the license will NOT restrict the licensee from publishing his own code or other 'materials' including, but not limited to, under an Open Source license. As a special note, it is observed that the Monty Program Ab Contributor Agreement itself fulfills these requirements. Also note that this promise does not not extend as a requirement to 3rd parties so as to restrict their rights to license products containing contributions. ********************************** We are especially interested to get feedback on the understandability of the last paragraph. henrik -- email: henrik.ingo(a)avoinelama.fi tel: +358-40-5697354 www: www.avoinelama.fi/~hingo book: www.openlife.cc

5 17

Re: [Maria-discuss] Information for release notes
by Daniel Bartholomew 28 Sep '09

28 Sep '09

Also posting this message to maria-discuss for those that might be interested in the changelog, but are not subscribed to maria-developers. On Thu, 24 Sep 2009 15:19:19 +0200, Kristian Nielsen <knielsen(a)knielsen-hq.org> wrote: Kristian> Hi Daniel, Kristian> Kristian> Here is a rough changelog written from reading through bzr Kristian> history. Kristian> Kristian> I took a dump of every commit in MariaDB that is not in MySQL Kristian> 5.1.38, and wrote this summary of the changes. Kristian> Kristian> I don't have sufficient knowledge to parse through all of the Kristian> Maria changes from before MariaDB started. Instead I wrote a Kristian> generic entry for the Maria storage engine, and also added Kristian> entries for what is already written (by Monty I think) on Kristian> http://askmonty.org/wiki/index.php/MariaDB_versus_MySQL Kristian> Kristian> So this is probably the best shot we have at a complete list Kristian> of relevant differences between MySQL and MariaDB. Do let me Kristian> know if anyone finds anything missing or any errors. Kristian> Kristian> Daniel, I hope you can use this as the basis for the release Kristian> notes. This list helps a lot. Thanks! Using the contents of the list, I have created a Changelog page on the wiki: http://askmonty.org/wiki/index.php/Manual:MariaDB_5.1_Changelog I organized the page into two sections: Features, and Bug Fixes. I also added links to the pages in the manual which exist for the changelog entries refer to. Kristian> Maybe this list will also be useful for you to fill out the Kristian> Manual on the Wiki. I am thinking you could check that all Kristian> new features are documented, and add pages for those that are Kristian> not. If not trivial, you could just make a stub page and ask Kristian> on maria-developers@ for someone to fill them out? Stub pages for the manual are easy to create: 1. add a link to the new page to http://askmonty.org/wiki/index.php/Manual:Contents 2. click on the new link 3. enter the following text into the new page: {{stub}} 4. save the new stub page To get things going, I created the following new stub pages for the manual: http://askmonty.org/wiki/index.php/Manual:Mysql_client_--abort-source-on-er… http://askmonty.org/wiki/index.php/Manual:XtraDB_storage_engine http://askmonty.org/wiki/index.php/Manual:Character_Set_Conversion_performa… http://askmonty.org/wiki/index.php/Manual:CHECKSUM_TABLE_performance Other stubs may need to be created, but I don't know which of the remaining topics need documentation or not. For example, does the entry about MariaDB NOT supporting NDB need it's own Manual page or not? Any contributions to the above stubs are *very* welcome. Any contributions to any of the other refman pages are likewise welcome: http://askmonty.org/wiki/index.php/Manual:Contents Henrik> Could the list itself be a basis for a changelog document and Henrik> then we make release notes into a more human readable document? Henrik> I thought that was your intention yesterday on IRC? The changelog page is a good compliment to the release notes page. The changelog is brief and is presented as a series of bullet points. The release notes page is longer with items presented as paragraphs in a more readable way. Thanks. -- Daniel Bartholomew

3 3

[Maria-discuss] License for MariaDB 5.1 Reference Manual
by Daniel Bartholomew 24 Sep '09

24 Sep '09

All, What license should we use for the MariaDB 5.1 Reference Manual? Some of the suggestions I've seen on IRC include: FDL : http://www.gnu.org/copyleft/fdl.html CreativeCommons : http://creativecommons.org My personal preference is to use the Creative Commons BY-SA license: http://creativecommons.org/licenses/by-sa/3.0/ This is the license used by Wikipedia and the share-alike part of the license ensures that the content remains open. It's a common license and is well understood and liked by a lot of people. Henrik mentioned the problem of attribution with CC licenses, but I don't think this is an issue with the mediawiki software we're using because of the edit histories and edit summaries, both of which fulfill this requirement. For example, the history page for the PBXT entry in the manual attributes me and Paul McCullagh for our contributions to the article: http://askmonty.org/wiki/index.php?title=Manual:PBXT_storage_engine&action=… I don't have much experience with the FDL, so if someone has reasons why we should use it, please share. Thanks. -- Daniel Bartholomew

3 2

[Maria-discuss] MariaDB 5.1 Reference Manual Introduction
by Daniel Bartholomew 22 Sep '09

22 Sep '09

All, The MariaDB 5.1 Reference Manual is progressing, but it needs an introduction. If you haven't taken a look at it yet, here is the TOC for the manual: http://askmonty.org/wiki/index.php/Manual:Contents At this stage we do not have a full or complete manual. Eventually we will have one, but creating it will take time. The purpose of the MariaDB 5.1 Reference Manual is to just document the differences between MariaDB 5.1 and MySQL 5.1 with the understanding that users can refer to the MySQL 5.1 manual for anything not covered in the MariaDB 5.1 manual. I'm currently working on an outline for the introduction page. One thing I think the intro should have is a version of the above paragraph to set expectations (we don't want users to think that we think our manual is complete). Beyond that, what other things should the introduction include? Also, if anyone knows of anything else which should be added to the manual, please let me know (or jump in and add it). Thanks. -- Daniel Bartholomew

1 0