One of the great things about the Internet is how it has made it easier to put great ideas into practice. Whether the ideas are about improving people’s lives or a new way to sell and old-fashioned product, there’s nothing like a good little startup tale of creative disruption to deliver us from something old and tired.
We raised topic of problems with flushing in InnoDB several times, some links:
This was not often recurring problem so far, however in my recent experiments, I observe it in very simple sysbench workload on hardware which can be considered as typical nowadays.
One lesson learned in more than two decades working in this industry is that most of the IT professionals are impatient, want to achieve results immediately, and, most importantly, they don't read documentation. Much as the average geek is happy to answer many requests with a dismissive RTFM, the same geeks are not as diligent when it comes to learning about new or updated technologies. For this reason, there is a kind of documentation that is very much appreciated by busy and impatient professionals: cookbooks.
During the past few months we’ve ran a couple of Oracle
Technology Network Developer Days focused on MySQL in the US. The events have
been a tremendous success and we got a lot of excellent feedback.
I saw yesterday that MySQL has finally done the right thing, and announced new commercial extensions.
What this means is that paying customers receive something more than users who get the community edition for free.
Believe it or not, when I was working in the community team at MySQL, I was already an advocate of this solution. You may see a contradiction, but there isn't. I would like to explain how this works.
MySQL 5.5 GA and MySQL 5.6 Development Milestone Releases have delivered many new compelling features to the MySQL users and community for testing, feedback and use.
In addition, commercial customers have access to a number of commercial extensions already included in MySQL Enterprise Edition:
Call for Papers for the Percona Live MySQL Conference and Expo is finally open! We had a little delay while we set up the software so thank you for your patience. Taking into consideration the short delay we are going to extend the close date to December 5th, 2011. Simply go to our website and click the Log In tab on the top of the page. Please help us make this conference outstanding by submitting your talks!
This week’s TGIF give-away contest is a day early, and it’s a guest post over on the Engine Yard blog: 5 subtle ways you’re using MySQL as a queue, and why it’ll bite you. Go there to read the full post, and watch @engineyard’s Twitter feed for the chance to enter the contest for free Percona Live London tickets!
Excerpt from the blog post:
Here’s a quick tip I know some of us has overlooked at some point. When doing SELECT … UNION SELECT, where do you put the the INTO OUTFILE clause? On the first SELECT, on the last or somewhere else? The manual has the answer here, to quote:
Only the last
SELECTstatement can use
INTO OUTFILE. (However, the entire
UNIONresult is written to the file.)