Tag Archives: mysql
I just finished reading a couple of interesting, and somewhat related, blog posts which I think are worth sharing (apologies to anyone who has already seen them). One is from Jelastic and the other is from Michal Hrušecký.
I’ve written about MariaDB and the Jelastic cloud before (see MariaDB now available as a hosted database via Jelastic cloud platform). Now Jelastic has published statistics on the relative popularity of the various databases they offer. The good news is MariaDB is currently the database of choice for 14% of their customers. The bad news is that we’re in fourth place behind their other three database choices (MySQL, PostgreSQL, and MongoDB). …
I suppose I should probably say “MariaDB στην Ελλάδα” which, according to Google Translate, is Greek for “MariaDB in Greece”. We’re still finalizing the arrangements, but I’m pleased to announce that the next Monty Program-sponsored MariaDB Developer Meeting will be held in (or near) Athens, Greece. Update: See below for hotel/location information.
Monty Program tries to hold two MariaDB Developer Conferences / Monty Program company meetings each year. The most recent one was held in Portugal this past March and it’s past time for another one. …
One thing which we, as developers of MariaDB, run into is that our personal database needs are not the same as many of our users. In fact, our needs are quite light compared to many. We have a MariaDB website, a company website, a knowledgebase, this blog, and that’s about it. None of them are particularly high traffic compared to what our customers have. But apart from talking to our customers, which are just a small percentage of the total MariaDB population, we wanted to have a way of finding out how MariaDB is used “in the real world”, so to speak. …
I just updated to Ubuntu 11.10 “Oneiric” on one of my desktops and I ran into an issue with MariaDB.
It’s not an issue with MariaDB itself, more in how the MariaDB “Natty” .deb packages are configured. We haven’t released .deb packages for Ubuntu 11.10 “Oneiric”, but the Natty packages work fine, apart from this one configuration issue (and when we do release “Oneiric” packages, they will work out-of-the-box).
The main problem is that some things have moved around in “Oneiric” and Apparmor doesn’t like the MariaDB “Natty” Apparmor defaults file because it doesn’t account for some of the new destinations. …
One could say that MariaDB now is 2 years old as a packaged product. The latest version, MariaDB 5.3 Beta, is the culmination of many years of hard work. We believe it contains the largest and most significant change to the code of MySQL since the launch of MySQL 5.0. I’m talking about the changes made to the central product component called the Optimizer.
Why did we touch something so central to the product? The fast answer is that the original Optimizer is about 17 years old. Prior to the work we did for MariaDB 5.3, the Optimizer hadn’t had any huge evolutionary improvements or changes in a decade (except for some features that were added in 2003-2005). …
Ben Forta, the author of MySQL Crash Course and Sams Teach Yourself SQL in 10 Minutes, has written what I believe is the first MariaDB-specific book: MariaDB Crash Course. I just received word from Ben that the book is now shipping.
Most MySQL books can, of course, be used to learn almost everything you need to know about using MariaDB. But with all of the features and abilities MariaDB has gained in the MariaDB 5.2 and MariaDB 5.3 releases, it’s nice there is now a book specific to MariaDB. …
There are many new features in MariaDB 5.3. I’m looking forward to many of them, but one of the ones I’m most excited about is Progress Reporting.
It’s a fact of life in the database world that some commands take longer to run than others. Commands like ALTER TABLE, LOAD DATA INFILE, and adding and dropping an index simply take time to run, depending (of course) on your data and schema. I always have hated having to wait for those commands to run with no indication of how much progress has been made or how much is left to do. …
In the #maria IRC channel the other day I fielded a question someone had about a DATETIME column where they wanted to SELECT by the year. The answer (which is probably obvious to many of you) is to use the YEAR() function like so:
select * from t1 where YEAR(d) = 2011;
(The above assumes the table is named “t1” and the DATETIME column is named “d”.)
In my reply I provided a link to the Date and Time Functions section of the AskMonty Knowledgebase, but when I looked at the entry for the YEAR() function, I noticed that the example given (which originated from the file scripts/fill_help_tables.sql which is found in the MySQL and MariaDB source) was not very helpful:
MariaDB [(none)]> …