PlanetMysql.ru — информация о СУБД MySQL

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.

You don’t need to know anything about MariaDB or MySQL in order to get the most out of this book. From the author’s website:

---

This is a beginner-intermediate book, and is not intended for SQL (including MySQL) experts. This book is for you if:

• You are new to SQL.
• You are just getting started with MariaDB and want to hit the ground running.
• You want to quickly learn how to get the most out of MariaDB.
• You want to learn how to use MariaDB in your own application development.
• You want to be productive quickly and easily using MariaDB without having to call someone for help.
• If you want to invest minimal time (and cost) for a crash course on one of the most important DBMSs out there, then this book is indeed for you.

---

The book is available from Amazon.com and other fine booksellers.

Enjoy!

 

PlanetMySQL Voting: Vote UP / Vote DOWN

I am happy to announce that the first MariaDB book is released!

The book is called MariaDB Crash Course and is written by Ben Forta, who also wrote the MySQL Crash Course book.

Quoting the book description:

"This book will teach you all you need to know to be immediately productive with MySQL. By working through 30 highly focused hands-on lessons, your MySQL Crash Course will be both easier and more effective than you'd have thought possible"

This is great news for new users to SQL and to MariaDB as it makes it easier for them to get things going quickly!

You can find a link to this book and other recommended MariaDB / MySQL books here.

Enjoy!


PlanetMySQL Voting: Vote UP / Vote DOWN

I am happy to announce that the first MariaDB book is released!

The book is called MariaDB Crash Course and is written by Ben Forta, who also wrote the MySQL Crash Course book.

Quoting the book description:

"This book will teach you all you need to know to be immediately productive with MySQL. By working through 30 highly focused hands-on lessons, your MySQL Crash Course will be both easier and more effective than you'd have thought possible"

This is great news for new users to SQL and to MariaDB as it makes it easier for them to get things going quickly!

You can find a link to this book and other recommended MariaDB / MySQL books here.

Enjoy!


PlanetMySQL Voting: Vote UP / Vote DOWN

Exciting news – MariaDB gets its first book!

Many years ago I read Ben Forta’s MySQL Crash Course . It is a book targeted at beginners of MySQL. Ben has now written another book, titled: MariaDB Crash Course.

Its still targeted at beginners, and covers many of the new features that are available in MariaDB up to version 5.2. I had the pleasure of pre-reading it, and did send in lots of comments to Ben, and if implemented we’ll see some stuff in there that is current even for MariaDB 5.3, like dynamic columns and more.

You can pre-order the MariaDB Crash Course which goes on sale September 23 2011 for USD$29.99 (Amazon lets you save, its $19.59 now). I’m not sure if we’ll see a Kindle version or not.

Related posts:

1. Opportunities to talk MariaDB/MySQL in Manila, Philippines
2. MariaDB at OSCON 2010
3. Where is MariaDB today?

PlanetMySQL Voting: Vote UP / Vote DOWN

MySQL 5.1 Plugin Development, by Sergei Golubchik and Andrew Hutchings. Packt Publishing, 2010. Executive summary: Highly recommended. If you want to develop MySQL extensions, buy this book. It's a must, written by two expert professionals who probably know more than anyone else on this matter. The book is full of practical examples explained with the theoretical information necessary to make it stick. This book fills a gap in the world of MySQL documentation. Although the MySQL docs are extensive and thorough, to the point that sometimes you wished that the writers were less verbose and stick more to the topic, when it comes to the plugin architecture, there are still more some unanswered questions. I guess that the ones who have implemented MySQL extensions so far have read the code, more than the documentation.

But, back to the point. The void is filled now, and in such a wonderful way! I have to disclose that I was the reviewer of this book, and while this fact puts me in a conflicting position when it comes to a review, it has also given me inner reason for praise, beyond the experience of a regular reader. The people who have worked with me will know that I am hard to please, and so my review was peppered with suggestions for improvements that, I admit it, made the authors' life quite difficult. I mostly complained that some of the examples proposed for each chapter were not enough useful and interesting. In short, there was not enough incentive for the reader to start coding immediately. I am glad to report that the authors were very responsive, and, rather than being annoyed by my demands, did work enthusiastically at the examples in the book until they became a true gem in this category. This book will surprise you for its practical approach, when it guides you through the examples, until you end up with a working extension.
The first chapter is probably the part that will save many hours of attempts to everyone who wants to build a plugin. In that chapter the authors explain how to build the different types of plugins in several operating systems. If you have ever tried to build a plugin, you will appreciate this chapter.
The book's body covers every type of plugin that you can create in MySQL, from the classic UDF to the more recent storage engine. For each chapter, you will have code ready to compile and try on your own, and the line-by-line explanation of what that code does, and why it was written the way it is.
Whenever the code is less than intuitive, the authors take care of it with additional theoretical and practical explanation, making sure that the reader is fully informed on the topic, and can complete the task effectively.
Summing up, this is not a book for the idle reader. It's a a practical help for the doers, the ones who want to get the job done, and need guidance through the maze of the MySQL plugin protocol.

Update. There is also a review at Slashdot.
PlanetMySQL Voting: Vote UP / Vote DOWN

Dear Kettle friends,

As mentioned in my previous blog post, copies of our new book Pentaho Kettle Solutions are finally shipping.  Roland, Jos and myself worked really hard on it and, as you can probably imagine, we were really happy when we finally got the physical version of our book in our hands.

So let’s take a look at what’s in this book, what the concept behind it was and give you an overview of the content…

The concept

Given the fact that Maria’s book called Pentaho Data Integration 3.2 was due when we started, we knew that a beginners guide would be ready by the time that this book was going to be ready.  As such we opted to look at what the data warehouse professional might need when he or she would start to work with Kettle.  Fortunately there is already a good and well known check-list out there to see if you covered everything ETL related and it’s called The 34 subsystems of ETL, a concept by Ralph Kimball that was first featured in his book The Data Warehouse Lifecycle Toolkit.  And so we asked Mr Kimballs permission to use his list which he kindly provided.  He was also gracious enough to review the related chapter of our book.

By using this approach we allow the users to flip to a certain chapter in our book and directly get the information they want on the problem they are facing at that time. For example, Change Data Capturing (subsystem 2, a.k.a. CDC) is handled in Chapter 6: Data Extraction.

In other words: we did not start with the capabilities of Kettle. We did not take every step or feature of Kettle as a starting point.  In fact, there are plenty of steps we did not cover in this book.  However, everywhere a step or feature needed to be explained while covering all the sub-systems we did so as clearly as we could.  Rest assured though; since this book handles just about every topic related to data integration, all of the basic and 99% of the advanced features of Kettle are indeed covered in this book

The content

After a gentle introduction into how ETL tools came about and more importantly how and why Kettle came into existence, the book covers 5 main parts:

1. Getting started

I hope that this overview of our new brain-child gives you an idea of what you might be buying into. Since all books are essentially a compromise between page count, time and money I’m sure there will be the occasional typo or lack of precision but rest assured that we did our utmost best on this one.  After all, we did each spend over 6 months on it…

Feel free to ask about specific topics you might be interested in to see if they are covered

Until next time,

Matt

PlanetMySQL Voting: Vote UP / Vote DOWN

Recent Tips and News on Java EE 6 & GlassFish:

GlassFish • An Eclipse / GlassFish / Java EE 6 Tutorial • Using JAX-RS with JDeveloper and Weblogic • GlassFish 3 and Oracle 10g XE on Ubuntu Linux 9.10 • Grizzly 1.0.38 has been released • Grizzly 2.0 RC2 has been released • Java Messaging Queuing – JMS (with GlassFish) • Messaging Queue – Handling Errors • Deploy Glassfish and mysql in Amazon EC2 • Using JAX-WS, JAX-RCP and GWT • Initialize log4j with an EJB 3.1 Startup Bean Converged Applications and SailFin • Glassfish Enterprise Server What Is Diameter Protocol? JavaEE 6 and Spring 3.0 • Java EE 6 and Spring 3.0 • Java EE 6 xor Spring • Java EE 6 (CDI / EJB 3.1) XOR Spring Core Reloaded Conferences • Java EE 6 & GlassFish @ JAX London & London JUG Trip Report • CFP: JavaOne Brazil (english, portuguese) New Books Covering GlassFish • Enterprise JavaBeans 3.1, Sixth Edition

PlanetMySQL Voting: Vote UP / Vote DOWN

According to a recent book about MySQL, this is the recipe to convert an IP address into an integer, with the purpose of using it as server-ID.

1. Take for example 10.0.159.22
2. Using a calculator (!!!), convert each of the four numbers to hexadecimal (you get 0a.00.9f.16)
3. Then glue the four hexadecimal numbers together, after removing the dots, and, again with the calculator, convert them to decimal (0a009f16HEX=167812886DEC)
4. Use this number (167812886) as your server ID in the options file.

Brilliant, eh?

Had the authors searched the MySQL manual for "IP address", they would have found the INET_ATON function, which can be used like this:

select inet_aton('10.0.159.22');
+--------------------------+
| inet_aton('10.0.159.22') |
+--------------------------+
|                167812886 |
+--------------------------+

PlanetMySQL Voting: Vote UP / Vote DOWN

The kind folks at O'Reilly sent me a fantastic book about MongoDB. This was a great read since it’s suited for people who do Operations and Development and Performance tuning (me). I've been using Cassandra for quite some time now (months lol) and the thing that has irritated me about Cassandra is the documentation for it. Cassandra documentation sucks, its hard to speed up on the internals. This MongoDB book is written by the most active participants that are developing MongoDB and the knowledge shows. What I like is it starts out on how to quickly get it up, add/get/update data to the DB. Then progresses to more advance topics-that talk about GridFS and MongoDB drivers. Personally I would like to see more elaboration of this facet in terms of motivation of why do this, what the win is and how it fits into the "Fast by Default" mantra. Each step is organized perfectly, and detailed with nice graphics that illustrate the document store or the flow of data from a systems view. When looking at the documentation on mongodb.org I see the same sort of clarity in this book. Comparing other NoSQL information, I do not see this transparency, which is rather frustrating because the learning curve is much larger. I'm so impressed with the info, and test results around the web that I'm moving to add this to my environment. Does this mean I'll get rid of my current Cassandra deployment? Probably not since its working great for my needs now.


Overall, great book, great info, intelligently presented with a straightforward explanation of how MongoDB works.
PlanetMySQL Voting: Vote UP / Vote DOWN

SQL Antipatterns, by Bill Karwin

I remember that when I finished reading The Lord Of The Rings, I felt a pang of disappointment. "What? Already finished? What am I going to read now? What can give me the same pleasure and sense of accomplishment that these wonderful pages have given me?"
That's how I felt when I came to the last page of SQL Antipatterns. And, no, Bill Karwin doesn't tell imaginary tales from a fictitious world. This book is full of very real and very practical advice, but all the material is presented with such grace and verve that I could not put it down until the very end. I read it cover to cover in just a few hours, and I savored every page.

What is this Antipatterns, anyway? The title may deceive a casual bookshop browser into believing that it's about some philosophical database theory. Digging further, you realize that it's a collection of best practice in database handling, but told from the side of the bad practice. Every chapter starts with the story of a disaster, followed by an explanation of why it happened, and how to recognize the symptoms. Along the way, you learn what people do to fix the problem when they don't understand where exactly the trouble comes from. And then comes the best practice section, where you are told of several ways of fixing the problem for good.
It's a pleasure from the start. When I read the introductory stories, I recognized mistakes that I have witnessed in my past experience and some that I made myself. It was a fascinating sequence of "look at this mess!", "Here is what you shouldn't do", "It happens when ...", and "this is what you should do".
The more I read, the more I wanted to read. And after a few chapters, a pattern appeared among the Antipatterns. The stories are not a casual collection of database mistakes. There is a thread. Most of the stories tell you what happens when you violate the relational theory principles, and the best practice solutions focus on how to apply relational principles in real life.
The relationship between the horror stories and the relational database theory becomes apparent when you get to the appendix. In other books, you can often skip the appendixes as a reminder of something that you know already. Not here. If you skip this one, you will miss a sort of Ellery Queen ending, where the detective puts together all the pieces of the mystery for the amazed audience.

I feel I would do a disservice to Bill if I revealed more about the book. I may have already spoiled some of the surprise by disclosing the inner structure of the book. But certainly I won't give away any of the juicy stories that make this book an invaluable tool for every database professional.
I can only say this. When I read a technical book, I usually find something wrong, or debatable, or some technical solution that I could improve upon. Not in this book. I completely agree with the theory and the practice that is suggested from start to finish. My QA ego suffers at the idea of not having found anything wrong, but this slight disappointment is more than compensated by the pleasure of reading such a beautiful book. Well done, Bill! I am already queuing to buy your next one!
PlanetMySQL Voting: Vote UP / Vote DOWN