News about the lawsuit between Oracle (which owns Java) and Google (which uses aspects of Java in Android) are resonating far and loud at the moment. At this point in the article, I should summarise the story: the trouble is that a summary at this point is impossible. The main problem is with Oracle, and their inability to understand free software.
Welcome to an introduction for the beginner to the basic manipulation of the MySQL database with free software. The purpose of this article is to show how universally straightforward it is to get started with installing and applying a high-grade enterprise ready database like MySQL, and to learn how to manipulate it via numerous free software approaches.
MySQL is one of the dominant players in the database market—a solid pillar in the Linux, Apache, MySQL and PHP or LAMP stack. SQL for MySQL Developers, written by Rick F. van der Lans and published by Addison Wesley covers all significant topics of SQL with specific references to the MySQL dialect.
One of the unique elements of MySQL is the ability to use a different storage engine to store your data. You can even mix and match storage engines within the same database.
Back in July, we made an Eclipse documentation plug-in of the MySQL manuals available for users to download.
In truth, the Eclipse documentation format is actually just HTML; you have to combine the HTML with a plug-in manifest that details the documentation, version number etc so that the documentation is loaded and identified as a valid plug-in element when Eclipse is started.
MySQL is a significant atom of a LAMP server. This amazingly fast database system is synonymous with PHP applications. Understanding the potentially complex details of views, stored procedures, merge tables, clustering, to name a few, can give your organization a competitive advantage. Pro Mysql, written by Micheal Kruckenberg and Jay Pipes and published by Apress, is a highly detailed account of the more advanced features of MySQL 5.0. A book well worth reading for those of you that want to become experts in this ever-evolving field.
Well, it's been completed a few weeks now, but I've finally reworked the Connector/MXJ and Connector/J sections of the MySQL Reference Manual, which in turn means the Connectors chapter has been completed.
One of the ongoing problems with documentation at MySQL is that it is getting ever larger.
Not only is the size of the docs increasing, but the formats and languages that we support is increasing too, and that is making it more and more difficult to effectively list them and make sure they are available.
Earlier this week I released the revamped Connector/NET documentation. This is part of the wider Connectors chapter rework, which I'm currently finishing by doing the Connector/J and Connector/MXJ documentation.
Connector/NET provides a full ADO.NET compatible interface to MySQL and is compatible both the Windows .NET and Mono installations.
We had a great question from a reader yesterday:
Is there a todo/nice-to-have list anywhere for MySQL documentation? Or perhaps a list of Devs who require documentation support? Or is all documentation a function of the core Documentation team?
Probably the most frequently asked question to the docs team at MySQL from the public is “I want to translate the manual into [insert language]”. That language can be anything from one we already have, through to some comparatively obscure suggestions.
I noticed this piece from Johan Andersson on Writing NDBAPI programs—connecting to MySQL Cluster last week, which shows you how to use the NDBAPI—the programming interface to the MySQL Cluster system. By coincidence, we enabled the NDBAPI documentation today. It consists of two elements:
This week, and specifically today, marks a minor milestone in my employment at MySQL—I’m finally a full time employee, no longer on probation. It has also been probably the busiest week since I started at MySQL, except for the week spent at the developers’ conference in Sorrento.
Why so busy?
Because I’ve spent many hours deep in the build process that actually generates the documentation, partly to address some existing errors, but also to improve the documentation after some new content was added. In summary, the following major steps were made this week:
Documentation is a vital part of any application, proprietary or free software, as it is often the first way to communicate with users about the application or software and how it should be used. I also think it tends to be one of the areas most taken for granted; most users expect it to be there and often forget just how much effort goes into producing it.
Many users also complain about the documentation itself. Often this is because it’s been written by programmers and, as a rule, they really aren’t that great at writing documentation that is particularly human readable.
As I mentioned here, I’m a member of the documentation team at MySQL, a job I started back in April. I’ve just completed a major tranche of documentation, and thought it would be interesting to let you guys know exactly what happens in a typical day for a member of the documentation team.