SkySQL today announced rapid growth and success in its first year of operations, fueled by new customers, partnerships and corporate growth. Highlights of the company's first year include:
Whenever I start a new project with MySQL or MariaDB I am tempted to jump in and start creating my schema and tables with nothing more than a basic outline of the requirements. Often the justification I give myself is that the sooner
One issue that developers often run into is needing or wanting to run a development version of MariaDB or MySQL on their desktop when there is already a production version installed. You may want to try out a new feature, or experiment with a patch, or maybe you're developing a new storage engine, or just having fun hacking on the code.
A common error in SQL is with quotes. Luckily, compared to other databases, MariaDB and MySQL are very forgiving.
For example, suppose I have a "products" table for an online store. If I want to look up every product which has a price of 5.99 or more I might use the following query:
A customer of ours had an interesting problem regarding a query that was taking too long, around 55s. Looking at the query with the query profiler we found that it was spending most of its time in the "statistics" phase.
Since 2005, April has been the month for MySQL users to meet in Silicon Valley, at the Santa Clara Convention Center. Traditionally, the conferences ended with an announcement of the dates for the following year. That was a good tradition.
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.
It has arrived, a little over a month from the last beta release, is MariaDB 5.3.1. It is a bug-fix update and as always the changelog lists everything that has been fixed. The release notes list all the changes present in the 5.3-series.
If you run a replicated MySQL setup and have a master failure, you may see the following error in your error log.
[ERROR] Error reading packet from server: Client requested master to start replication from impossible position ( server_errno=1236)
At this point your slave will not be replicating and you will need to recover from the situation. But why did it occur in the first place and what does it mean to your data integrity?
We have seen a few instances where upgrades of MySQL 5.1 to 5.5 have resulted in poor performance when using default values. After investigation it would appear that the main culprit appears to be the innodb_thread_concurrency setting.