MySQL

The world's most popular open source database

Contact a MySQL Representative


  • MySQL.com
  • Developer Zone
  • Partners & Solutions
  • Customer Login
  • DevZone
  • Downloads
  • Documentation
  • Articles
  • Forums
  • Bugs
  • Forge
  • Blogs
 
  • You are currently browsing the archives for the MySQL Server category.

  • Pages

    • About me
    • Bio
    • Press Release: “Kaj Arnö Appointed MySQL VP of Community Relations”
  • Archives

    • October 2008
    • September 2008
    • August 2008
    • July 2008
    • June 2008
    • May 2008
    • April 2008
    • March 2008
    • February 2008
    • January 2008
    • December 2007
    • November 2007
    • October 2007
    • September 2007
    • August 2007
    • July 2007
    • June 2007
    • May 2007
    • April 2007
    • March 2007
    • February 2007
    • January 2007
    • December 2006
    • November 2006
    • October 2006
    • September 2006
    • August 2006
    • July 2006
    • June 2006
    • May 2006
    • April 2006
    • March 2006
    • February 2006
    • January 2006
    • December 2005
    • November 2005
    • October 2005
    • September 2005
  • Categories

    • Architecture of Participation (55)
    • Connectors (12)
    • Documentation (4)
    • Events (50)
    • Falcon (5)
    • GPL (9)
    • GUI (3)
    • Licensing (12)
    • MySQL (219)
    • MySQL Cluster (5)
    • MySQL Proxy (4)
    • MySQL Server (32)
    • MySQL Users Conferences (27)
    • MySQL Workbench (5)
    • Photography (11)
    • PHP (9)
    • Release Policy (20)
    • Ruby on Rails (5)
    • Running (6)
    • Summer of Code (8)
    • Sun (53)
    • Sun visits (24)
    • Travel (22)
    • Uncategorized (1)
    • Use cases (12)
    • Virtual company (37)



Observations by Kaj Arnö @Sun

Archive for the ‘MySQL Server’ Category

« Previous Entries
Next Entries »

MySQL University, MEM_ROOT and Pillows

Thursday, March 1st, 2007

I’m listening to the first MySQL University session. It’s the highest form of education available at MySQL AB, hence the name. Not about how to use MySQL, but how to write code patches for MySQL.

Right now, Sergei Golubchik is sitting in Cologne, Germany, speaking behind Skype Conferencing and two pillows (sound quality!) about memory management and mysys libraries and algorithms. Monty and others are assisting Sergei over our internal IRC, where there are 31 developers listening in.


Our presenter, Sergei Golubchik, in a non-virtual setting

Here’s an IRC transcript:


monty|uni ie, only destructior is called, memory is not freed until free_root()
rafal|school monty|uni: if I initialize String from other String, or char table[] or “string constant”, is memory allocated/deallocated correctly?
iggy|uni serg, While talking about alloc/dealloc for Strings, could you comment on the usefullness of SAFEMALLOC and how to take advantage of it?
monty|uni rafal|school: should be
rafal|school monty|uni: ok (thanks for all answers)
monty|uni Note that String can be both a pointer (like char*) and a C++ like string that holds the string itself
monty|uni If you use it as a pointer, you don’t get it freed. If you use it as a string (or convert it from pointer to string with String.copy(), you need to free it
monty|uni Using delete works on both cases
monty|uni so to be safe, you should just call delete on all String objects.
rafal|school monty|uni: how String can be used as a pointer?
mats|phone monty|uni, So that means that you have to allocate memory for a C string if you are passing it into the String constructor?
monty|uni Default is pointer
monty|uni mats|phone: or you use string.copy()

It’s a challenge. I’m not talking about understanding the routines, like

  • init_alloc_root() - Initalize a MEMROOT object
  • alloc_root() - Allocate an object
  • multi_alloc_root() - Allocate many objects at once
  • free_root() - Free everything

nor about understanding Serg’s accent. Everyone at MySQL has an accent. Our internal language is Bad English, and I feel competent to conform.

The challenge is the low bandwidth. I’m also sitting in Germany, and sadly, it sounds as if Serg were speaking through two pillows.

So why am I writing about this? Because we are planning to open up MySQL University. We are thinking of moving the IRC chat to freenode, and the Wiki pages to the MySQL University Library on MySQL Forge Wiki. The sound already is public, on Skype Conferencing.

With the open MySQL University, those who have an interest in learning about MySQL’s internal code structure can listen in, or follow the MP3 recording later on, or just browse the MySQL University Library. Stay tuned — we hope to be able to open up these weekly sessions later on in March.

Posted in Architecture of Participation, MySQL, MySQL Server | No Comments »

Launching the Quality Contribution Program

Tuesday, February 20th, 2007

I’m happy to now announce the full Quality Contribution program tentatively described in December.

Some basics: We understand that the main reason users report bugs is to get them fixed. That said, we still think we have plenty of opportunities of improving our ways when it comes to making it easier for you to help us.

The Quality Contribution Program goal is to improve the quality of MySQL products, with the active co-operation of the MySQL user community. The program facilitates this by

  1. visibly acknowledging the participants by attributing individual quality enhancements to them;
  2. rewarding the participants with benefits in proportion to their contribution (Awards are subscriptions to MySQL Enterprise);
  3. streamlining the process of contributing to MySQL Quality for the benefit of both current and future contributors

Quality Contributions fall into three categories: (i) bug reports, (ii) test cases, and (iii) code patches. We evaluate each contribution with a publicly verifiable set of rules, and the contributor accumulates the QA points for all contributions submitted during the last 12 months.

The award is MySQL Enterprise subscriptions:

Candidate: someone who has started doing contributions
Basic: a proven contributor, who has submitted material, earning at least 50 QA points and a
MySQL Enterprise Basic subscription;
Silver: a very productive contributor, earning at least 200 QA points and a MySQL Enterprise
Silver subscription;
Gold: a phenomenal contributor, who has earned at least 500 QA points and a MySQL Enterprise
Gold subscription;
Platinum: The contributor that makes the headlines, having delivered contributions up to 1000
QA points and thus getting a MySQL Enterprise Platinum subscription;

And let me thank the 60 Quality Contributors that have already enrolled! Specifically, I want to list by name the topmost 20 contributors, to which MySQL and its user community is greatly indebted:

Top contributors

No name QA points level
1 Martin Friebe 306 Silver
2 Beat Vontobel, MeteoNews AG 285 Silver
3 Debian user community 264 Silver
4 Heinz Schweitzer 243 Silver
5 Carl F. Karsten, dabodev.com 207 Silver
6 Jared Sullivan, Paradigm IT Solutions 153 Basic
7 Olaf van der Spek 150 Basic
8 Peter Laursen, Webyog Softworks Private Limited (”Webyog”) 135 Basic
9 Jocelyn Fournier, www.mesdiscussions.net 132 Basic
10 Peter Zaitsev, MySQLPerformanceBlog.COM 130 Basic
11 Gisbert W. Selke, TapirSoft 126 Basic
12 John Yodsnukis, dbbd.net 100 Basic
13 Paolo “pabloj” Magnoli, pabloj.blogspot.com 99 Basic
14 Dave Pullin, ColdLogic LLC 96 Basic
15 Andreas Påhlsson 90 Basic
16 Jeremy Cole, Proven Scaling LLC 90 Basic
17 Marc Castrovinci, Smartonline.com 90 Basic
18 Yoshiaki Tajika, NEC System Technologies 80 Basic
19 Roberto Spadim, Spadim Technology / Brazil 75 Basic
20 Stefaan “Annunaki” Lesage, PeopleWare N.V. 72 Basic

For us to be able to accept test cases and bug patches from a legal perspective, we have to ask our contributors to agree to our Contributor License Agreement, which exists in a click-through form. Should you have any questions on this or other matters, please contact Giuseppe Maxia and/or myself at firstname@mysql.com.

So please enroll in the program and help us identify, test and fix our bugs!

Posted in Architecture of Participation, MySQL, MySQL Server | 2 Comments »

MySQL continues providing Windows binaries for free

Thursday, January 18th, 2007

Contrary to some reports in the community, MySQL will continue providing binaries both for Windows and other operating systems. All our download pages, including those for MySQL 5.0, have binaries today, and will continue to have them.

The source-only releases we introduced with 5.0.33 (and will continue to provide in the future)are just in addition to the binary-and-source releases. The current latest binary-and-source MySQL Community Server release is 5.0.27, and I expect MySQL 5.0.35 Community Server to be released as binary-and-source within a month, both for Windows and our other platforms. This is as we always planned it, and tried to communicate it. I am sorry our communication has not been clear enough.

Posted in Licensing, MySQL, MySQL Server, Release Policy | 5 Comments »

MySQL 5.0.33 Community Server released

Wednesday, January 10th, 2007

MySQL Community Server 5.0.33 has now been released. It is a pure bugfix release, delivered in a source-only form as a tarball for Unix and for Windows (we provide separate sources for these, as the build procedure differs) on dev.mysql.com/downloads/mysql/5.0.html#Source.

The release contains all bug fixes applied to MySQL Server 5.0 since the last Community release 5.0.27 in October 2006. The jump in numbers from .27 to .33 is to make it clear that .33 is up-to-date to the level of MySQL Enterprise Server 5.0.32, released about two weeks ago. We reserve the even version numbers for MySQL Enterprise, while odd version numbers indicate a Community Server Release. Both use the same “5.0″ version part, as they share the same code base.

We are in the process of applying several patches provided by Community members, currently in our Contributions Pipeline. I expect several of these enhancements to be merged soon enough for the next MySQL Community Server to be released in February as 5.0.35. On the contrary, they will not appear in MySQL Enterprise Server 5.0.

The release notes for MySQL 5.0 have been split into separate sections of the MySQL 5.0 reference manual. This means that the documentation of the bug fixes of MySQL Enterprise Server 5.0.28, 5.0.30 and 5.0.32 have been copied into the release notes for MySQL Community Server 5.0.33.

The purpose of this MySQL Community Server release is twofold:

a) to deliver recent, fresh bug fixes to the MySQL community
b) to establish and test the practice of source tarball releases

As such, the bug fixes have been available in source form both as part of the BitKeeper source repository on mysql.bkbits.net and as MySQL Enterprise Server source releases on our ftp site ftp.mysql.com. However, we believe Linux distributions and Open Source fluent community users of MySQL are better served by a tagged MySQL Community Server release, which is available on our download server and has one single set of release notes.

Through establishing source tarball releases, we follow the tradition of many other FOSS projects. This provides more possibilities for Community Contributions in the means of binary builds.

We refer to our reference manual, especially the chapter 2.4.14. MySQL Installation Using a Source Distribution when it comes to building MySQL Community Server. At the same time, I want to point out that the service of providing MySQL Enterprise Server binaries is something we do for our paying customers, in the form of the MySQL Enterprise Server subscription, starting at 595 dollars a year.

We strive to release MySQL Enterprise Server on a monthly basis. While we don’t have a specific schedule or policy for when MySQL Community Server is released in binary form, I expect the next Community release, 5.0.35, to be available as source and binaries for the same platforms as MySQL Enterprise Server and as the previous MySQL Community Server binary release 5.0.27. Until that point in time, the 5.0.27 binaries will be the ones listed on the normal MySQL 5.0 download pages at dev.mysql.com/downloads/mysql/5.0.html.

Distributors of MySQL Community Server are welcome to contact Colin Charles and Lenz Grimmer, with proposals for process improvements (at firstname@mysql.com. Better still, subscribe to the packagers@lists.mysql.com archived and public mailing list at lists.mysql.com/packagers, which Colin and Lenz are monitoring. That list as our discussion forum for builders of MySQL releases, both already existing ones like the various distributors, and for new community contributors that want to step up and provide binaries, including Windows.

Please note that while the release has undergone testing, 5.0.33 is our first source only MySQL Community Server release, so I expect there to be some room for process improvement on our side.

Amongst the bug fixes, there is one that I want to highlight. It is listed as the innocent-looking bullet “InnoDB showed substandard performance with multiple queries running concurrently. (Bug#15815)“. This is a fix to an issue especially surfacing on multiple-core processors. You testing in such environments is much appreciated. As a reference, you may want to read the Bugs database entry bugs.mysql.com/15815 as well as two articles from Peter Zaitsev — one from a week ago, another from last September.

Posted in Architecture of Participation, MySQL, MySQL Server, Release Policy | 2 Comments »

MySQL Community Server recap

Wednesday, January 3rd, 2007

As I have seen some concerns about the release schedule of MySQL Community Server and the availability of MySQL Enterprise Server sources, let me recap and detail some of the plans, which haven’t changed since the introduction of MySQL Enterprise Server in October:

  1. MySQL 5.0 Community Server sources and binaries are available from our download pages. The latest version is 5.0.27, released in October.
  2. MySQL Enterprise Server is released more frequently than MySQL Community Server. This means that we’ve seen also 5.0.28, 5.0.30 and 5.0.32 being released for MySQL Enterprise Server. Even numbers are for Enterprise, odd numbers for Community.
  3. MySQL Community Server gets all bug fixes from MySQL Enterprise Server. This means that the next MySQL Community Server will contain all bug fixes from the most recent MySQL Enterprise Server published at that point. If we’re releasing a MySQL Community Server right after MySQL Enterprise Server 5.0.34, it will be labeled 5.0.35 and contain all 5.0.34 fixes plus any community patches applied at that point in time.
  4. The higher release frequency of MySQL Enterprise Server provides added value for our commercial customers. We intend to deliver predictable monthly Enterprise releases. Providing and verifying frequent binaries is a paid-for service for those who want to spent money to save time. That said, MySQL continues to provide new community binaries from time to time, as said in item 1 above.
  5. MySQL Community Server additionally includes what we call Community Enhancements on top of MySQL Enterprise Server. However, we’ve been slow at applying these enhancements. Jeremy Cole and others have been contributing patches, and we are looking at getting several of his enhancements and those of others into the tree ASAP. We are also looking at improving our processes so that contributors won’t have to wait as long in the future.
  6. MySQL Enterprise Server is available in source form for download from our ftp server at ftp.mysql.com. We don’t highlight this much, as we would like to encourage our community users — including Linux distributions — to use our community server.
  7. The MySQL Community Server tree is updated frequently with the bug fixes from the Enterprise tree. Our users can access both Community and Enterprise server from BitKeeper. However, we expect most users to want to work from tagged, numbered releases, no matter whether they use Community or Enterprise server.

One area where we feel the need to improve is the release frequency of source tarballs from the Community Tree. This will alleviate some of the burden put on a couple of Community users. Our current plan is to have the next MySQL Community Server source tarball release happen late January or early February.

Posted in MySQL, MySQL Server, Release Policy | 3 Comments »

MySQL 4.0 has reached the final stage of its lifecycle

Thursday, December 14th, 2006

MySQL 4.0 has now reached the final stage of its active development life cycle. As I noted on 12 July 2006 when announcing the MySQL Lifecycle Policy, keeping legacy versions of our software alive is expensive and time-consuming. While we know that database administrators hate to upgrade their databases, we believe that the vast majority of our customers and our community are better served by us focusing our attention on newer releases. However, we don’t want to abandon users of our older products — so we are asking them to help subsidise the cost themselves.

This means that those who wish to continue to receive our support for MySQL 3.23 and MySQL 4.0 will need to be covered by a MySQL Enterprise subscription, starting 1 Oct 2006 for MySQL 4.0.

In practice,

  1. We are no longer producing new binary updates for MySQL 4.0 for the
    general public.
  2. Soon, we will be removing the archived versions of old MySQL 4.0
    binaries from our web site.
  3. The MySQL 4.0 source code will remain available on our web site in tarball format.

As a general rule, we encourage everyone to upgrade from MySQL 4.0 to a newer release.

However, those who wish to continue to get support for MySQL 4.0 during its Extend Lifecycle Timeframe (which will continue for another two years until 31 Dec 2008) are referred to the MySQL Enterprise subscription service.

A MySQL Enterprise subscription will not only give you access to support for older versions, but also assistance with migrating to the most current production release, MySQL 5.0.

Posted in MySQL, MySQL Server, Release Policy | 3 Comments »

Introducing the MySQL Community Server and the MySQL Enterprise Server

Tuesday, October 17th, 2006

Today, you will see an announcement of a new flagship commercial offering from our company, called MySQL Enterprise. I want to explain to you why we are making these changes to our business — and to the delivery of our software.

We recognise that the needs of the MySQL Community are different from the needs of commercial enterprise customers. After 11 years of producing our software, we can no longer hope that a single offering is the best solution for both Community and Enterprise users. Consequently, we are introducing two different offerings for each distinct target group.


The MySQL Community Server is:

  • for the Open Source fluent audience, do-it-yourself (DIY)
  • for those who don’t need support
  • free-of-charge

The MySQL Enterprise Server is:

  • for the non-DIY commercial user
  • part of the ‘MySQL Enterprise’ subscription offering
  • for those who want extra help developing, deploying and managing MySQL DBs
  • coupled with access to MySQL technical support
  • assisted by new automated DBA monitoring and advisory services

With this differentiation, we aim to better serve both categories of MySQL users — those who are willing to spend time to save money, and those who are willing to spend money to save time.

If our changes succeed in their objective, both audiences will benefit from a more stable, feature-rich and high-quality database. The open source benefits for each of the audiences mutually reinforce each other:

  • Community users get new features at no-cost to them — funded by paying customers
  • Enterprise users get a more stable, reliable and predictably-released product — thanks to community participation

Each of these components of the virtuous circle of open source contributes to the development and spreading of a better MySQL for everyone.

By the name MySQL Enterprise, we want to make clear that this is the offering we expect business users of MySQL to be interested in: Are you using MySQL in a production enterprise setting? Go for MySQL Enterprise!

We believe the users of MySQL Community Server expect

  • early access to MySQL features under development
  • that MySQL AB will listen to their input
  • timely corrections to bug fixes they report
  • help with enhancing MySQL for their particular needs
  • channels to communicate with the rest of community for getting assistance
  • an easier process for having contributions accepted in MySQL
  • commitment to Open Source — including free, unrestricted availability of source code

and this is what we will continue to deliver.

We’re happy to note the growth in contributions flowing into MySQL and its ecosystem. To facilitate these, we have

  • launched MySQL Forge (see forge.mysql.com)
  • established a Contribution License Agreement (see MySQL_Contributor_License_Agreement on Forge Wiki)
  • supported a MySQL Community Camp (see mysqlcamp.org)
  • started to Doxygen comment our code for easier understandability (see CommunityDoxygenProject on Forge Wiki)

and this is now showing results:

  • 159 Forge projects by 58 distinct contributors
  • 44 Forge snippets by 25 distinct contributors
  • 361 forge users registered
  • 1696 distinct Forge Wiki page titles
  • 184 Forge wiki contributors
  • MySQL Server kernel contributions accepted, such as Jeremy Cole’s

On top of this, we expect to soon launch a competition for voting on the look-and-feel of our new MySQL Community Server logotype and Web site. We will also be establishin a pilot program for MySQL Quality Assurance contributors. Most importantly, we’re launching the MySQL Winter of Code program, featuring the Connectors Contest and the Storage Engines Encounters, which I will be telling you about separately next week.

Technically, the MySQL Enterprise Server inherits the current MySQL 5.0.26 code base, as does the MySQL Community Server. However, we will be encouraging and incorporating contributions in the form of minor enhancements and experimental features already into the 5.0 version of MySQL Community Server. This way, contributors don’t have to wait until the next major release for their improvements to get into use, and enterprise users can continue using 5.0 without seeing any destabilisation of the code base due to new functionality being introduced.

As part of our differentiation, we will do more frequent binary releases of the MySQL Enterprise Server software than of the MySQL Community Server. However, all of our database software is open source, so we will continue to make all releases available over our BitKeeper tree and as source code tarballs — even if the MySQL Enterprise Server binaries will not be available for public download but limited to our commercial customers and our core QA contributors.

Finally, we will continue to be active good citizens in the greater Free and Open Source Software world. We’re participating in the GPLv3 drafting process, we’re supporting the Free Software Foundation as FSF corporate patrons, and we’re supporting campaigns against the spread of software patents around the globe.

So: Click here to see today’s press releases on MySQL Enterprise, which describes our new flagship commercial offering, directed at paying enterprise customers. It refers to the MySQL Network Monitoring & Advisory Services, which is a commercial only offering we are about to launch. In due course, I’ll be sharing more about that with you. Stay tuned, and please give me your feedback on what you think (including private email to k a j at m y s q l . c o m)!

Posted in MySQL, MySQL Server, Release Policy | 9 Comments »

MySQL Lifecycle Policy

Wednesday, July 12th, 2006

Database administrators hate to upgrade their databases. At MySQL, we like to think that we have been early to recognise this, and we have given more or less unlimited support to even very old releases, on a multitude of platforms. However, this has not been without cost to ourselves.

Many of our users know that the cost of maintaining several releases is high. We have thus been asked to clarify our support lifecycle policy. After long internal discussions, that were not always easy, we are now pleased to say that we have an explicit support lifecycle policy. It addresses the timeframes we will provide updates and continued support for current and older versions of the MySQL server.

Keeping older versions alive for a long time is appreciated by our community and our customers alike. However, we are no longer in a position to maintain our older versions without remuneration. This means that those wishing to enjoy MySQL’s support in their usage of MySQL 3.23 and MySQL 4.0 need to plan for their future, as our support of these releases will be limited to those covered by a MySQL Network subscription, starting in 1 Aug 2006 (for MySQL 3.23) and 1 Oct 2006 (for MySQL 4.0).

This means that we are no longer offering publicly available binary updates for our 3.23 and 4.0 releases. The sources of these will still be provided. We are also evaluating whether we will continue hosting archived versions of old binaries, as well as the timeline for the support of MySQL 4.1.

We hope the clarity offered by this explicit support lifecycle policy will give a good base to our Customers and Users alike, when planning for their future use of MySQL!

Posted in MySQL, MySQL Server, Release Policy | 4 Comments »

Announcing MySQL 5.1 alpha: Partitioning & Co.

Monday, December 5th, 2005

MySQL 5.0 has been downloaded over four million times: two before GA, and two after GA. We’re proud of these numbers. But life does not stop at MySQL 5.0.

So we have now announced the first public version of MySQL 5.1 alpha. Remember, alpha at MySQL means that we’re still adding features.

One of the hottest new features is partitioning. Partitioning allows distributing portions of individual tables across a filesystem, according to rules which can be set when the table is created.

In effect, different portions of a table are stored as separate tables in different locations - but the user still sees the partitioned table as a single table.

If you have datasets of several terabytes, we would be very happy if you help us out with some testing.

Posted in MySQL, MySQL Server | No Comments »

Announcing MySQL 5.0

Tuesday, October 25th, 2005

Dear user of MySQL,

It is my pleasure to announce the production release of MySQL 5.0, which is hereby GA (Generally Available). Since my announcement of the Release Candidate less than a month ago, no bugs have been reported that require a second Release Candidate. This, combined with the feedback from over two million downloads of MySQL 5.0 during its beta phase, give us the confidence to give MySQL 5.0 the status of Current Production Release, or GA.

In the Release Candidate announcement less than a month ago, I described MySQL 5.0 as “the most important release in MySQL’s history”, and that is certainly the case. Thus, I encourage you all to:

  • get your own copy at http://dev.mysql.com/downloads/mysql/5.0.html
  • do all of your new database development using MySQL 5.0
  • upgrade your current MySQL environments to MySQL 5.0, as soon as you’ve properly verified your production applications against it (be sure to take a full backup of your data before upgrading, study the relevant documentation, and if you have a MySQL Network support contract, consult first with the MySQL Support Team)

Let me also underline that we continue to offer some earlier versions of MySQL Server for download. However, you should expect maintenance releases for earlier versions only in limited form:

  • for MySQL 4.1, only when serious bugs affecting significant user groups are reported
  • for MySQL 4.0, only when security bugs are reported

MySQL 5.0 is the most ambitious release to date for MySQL AB. We have added functionality that our users have requested from us over many years. However, everything we do at MySQL centers around our three priorities of Performance, Reliability, and Ease of Use. MySQL 5.0 is certainly true to these company-wide values.

Key new features of MySQL 5.0 come in three groups:

  1. ANSI SQL standard features formerly unknown to MySQL
  2. ANSI SQL standard compliance of existing MySQL features
  3. New MySQL Storage Engines, Tools and Extensions

1. The new ANSI SQL features include:

  • Views (both read-only and updatable views)
  • Stored Procedures and Stored Functions, using the SQL:2003 syntax, which is also used by IBM’s DB2
  • Triggers (row-level)
  • Server-side cursors (read-only, non-scrolling)

2. Implementing ANSI SQL standard ways of using existing MySQL features means there will be fewer unpleasant surprises (”gotchas”) for those migrating to MySQL from other database systems:

  • Strict Mode: MySQL 5.0 adds a mode that complies with standard SQL in a number of areas in which earlier versions did not; we now do strict data type checking and issue errors for all invalid dates, numbers and strings as expected
  • INFORMATION_SCHEMA: An ANSI SQL-compliant set of tables that provide database metadata, in parallel with the MySQL-specific SHOW commands
  • Precision Math: A new library for fixed-point arithmetic, giving high accuracy for financial and mathematical operations
  • VARCHAR Data Type: The maximum effective length of a VARCHAR column has increased to 65,532 bytes; also, stripping of trailing whitespace no longer occurs

3. New MySQL Storage Engines, Tools and Extensions are:

  • XA Distributed Transactions
  • ARCHIVE Storage Engine for storing large amounts of data without
    indexes in a very small footprint, intended for historical data that
    may be needed for future audit compliance (Sarbanes Oxley or
    otherwise)
  • FEDERATED Storage Engine for accessing data ín tables of remote
    databases rather than in local tables (only in MAX version)
  • Instance Manager: a tool to start and stop MySQL Server, even remotely

To find out more details on what’s new in MySQL 5.0, follow the pointers from http://dev.mysql.com/doc/mysql/en/mysql-5-0-nutshell.html

To find out the changes specific to MySQL 5.0.15 in relation to 5.0.13 (the release candidate), see the two files http://dev.mysql.com/doc/mysql/en/news-5-0-14.html and http://dev.mysql.com/doc/mysql/en/news-5-0-15.html (5.0.14 was not released publicly).

MySQL 5.0 is also reflected in our GUI tools and Connectors:

MySQL Administrator 1.1.4 and MySQL Query Browser 1.1.17 are aware of the new MySQL 5.0 features. They can be used to write and test stored procedures, create views, include them in scheduled backups and much more.

The latest shipping versions of our Connectors work with MySQL 5.0, and all connectors (MySQL Connector/ODBC, Connector/J and Connector/NET) support all MySQL 5.0 flagship features.

Of course, we recognize that any piece of software contains bugs. We continue to need your involvement to ensure that MySQL 5.0 is the best that it possibly can be. Should you find any issues in MySQL 5.0, report them through our bug-reporting system at http://bugs.mysql.com/ and we will improve upon MySQL 5.0 in upcoming maintenance releases.

The MySQL team looks forward to your input

  • in our MySQL Forums at http://forums.mysql.com/
  • in the bug database at http://bugs.mysql.com/
  • in our mailing lists at http://lists.mysql.com/
  • in the PlanetMySQL blog aggregation via http://www.planetmysql.org/newfeed.php
  • in the User Comments of our manual at http://dev.mysql.com/doc/mysql/en/index.html (specifically for Documentation comments)
  • and in the form of downloads from http://dev.mysql.com/downloads/mysql/5.0.html

MySQL 5.0 is available now. Go download it, install it, and take benefit from its many new features.

And do keep us informed on how MySQL can help support you!

Kaj Arnö
VP Community Relations
MySQL AB

Posted in MySQL, MySQL Server, Release Policy | No Comments »

« Previous Entries
Next Entries »

Observations by Kaj Arnö @Sun is proudly powered by WordPress MU running on Blogs.mysql.com.
Entries (RSS) and Comments (RSS).