Showing entries 1 to 9
Displaying posts with tag: EOL (reset)
The curse of MySQL warnings

MySQL warnings are an anti-pattern when it comes to maintaining data integrity. When the information retrieved from a database does not match what was entered, and this is not identified immediately, this can be permanently lost.

MySQL by default for several decades until the most recent versions enabled you to insert incorrect data, or insert data that was then truncated, or other patterns that resulted in failed data integrity. Very few applications considered handling warnings as errors, and there is a generation of software products that have never informed the developers that warnings were occurring.

The most simplest example is:

CREATE SCHEMA IF NOT EXISTS warnings;
USE warnings;

CREATE TABLE short_name(
  id INT UNSIGNED NOT NULL AUTO_INCREMENT,
  name VARCHAR(20) NOT NULL,
  PRIMARY KEY(id)
);

INSERT INTO short_name (name) VALUES ('This name is too long and will get truncated');
ERROR 1406 (22001): Data too long for …
[Read more]
Into the sunset

After four years working with the MySQL team, under three different companies, it's time for me to pursue a new career.

Tomorrow is my last working day at Oracle. (Working? But it's Sunday! So, ehm, kind of, anyway, you got the point.)

You may look at my personal blog in the coming days to know what I am going to do next.

Right now, I would like to just say thank you to all my colleagues in the MySQL Team, and to all the community people with whom I have shared the wonderful experience of these four years.

And also, thanks to all the ones who have offered me a job. Really. There were many offers. I am sorry I could not …

[Read more]
Into the sunset

After four years working with the MySQL team, under three different companies, it's time for me to pursue a new career.

Tomorrow is my last working day at Oracle. (Working? But it's Sunday! So, ehm, kind of, anyway, you got the point.)

You may look at my personal blog in the coming days to know what I am going to do next.

Right now, I would like to just say thank you to all my colleagues in the MySQL Team, and to all the community people with whom I have shared the wonderful experience of these four years.

And also, thanks to all the ones who have offered me a job. Really. There were many offers. I am sorry I could not …

[Read more]
Into the sunset

After four years working with the MySQL team, under three different companies, it's time for me to pursue a new career.

Tomorrow is my last working day at Oracle. (Working? But it's Sunday! So, ehm, kind of, anyway, you got the point.)

You may look at my personal blog in the coming days to know what I am going to do next.

Right now, I would like to just say thank you to all my colleagues in the MySQL Team, and to all the community people with whom I have shared the wonderful experience of these four years.

And also, thanks to all the ones who have offered me a job. Really. There were many offers. I am sorry I could not …

[Read more]
Active support for MySQL 5.0 and extended support for 4.1 will soon end

At the end of this year, two long lasting versions of MySQL will fall off the radar, each of them in a different way.

MySQL 5.0 active support will end.

What does that mean? it means that there won't be regular monthly updates and bug fixes. This version enters the extended support period, which lasts until 2012. During this phase, only security and major bugs fixes will be applied.

MySQL 5.0 will still be available in the download pages for two more years, and any security updates will be released on those pages.

The previous version, MySQL 4.1, instead, will be retired completely. It has ended its extended period. As such, it will be removed from the download page, and also from the download archives. Next year, if you want …

[Read more]
Active support for MySQL 5.0 and extended support for 4.1 will soon end

At the end of this year, two long lasting versions of MySQL will fall off the radar, each of them in a different way.

MySQL 5.0 active support will end.

What does that mean? it means that there won't be regular monthly updates and bug fixes. This version enters the extended support period, which lasts until 2012. During this phase, only security and major bugs fixes will be applied.

MySQL 5.0 will still be available in the download pages for two more years, and any security updates will be released on those pages.

The previous version, MySQL 4.1, instead, will be retired completely. It has ended its extended period. As such, it will be removed from the download page, and also from the download archives. Next year, if you want …

[Read more]
Active support for MySQL 5.0 and extended support for 4.1 will soon end

At the end of this year, two long lasting versions of MySQL will fall off the radar, each of them in a different way.

MySQL 5.0 active support will end.

What does that mean? it means that there won't be regular monthly updates and bug fixes. This version enters the extended support period, which lasts until 2012. During this phase, only security and major bugs fixes will be applied.

MySQL 5.0 will still be available in the download pages for two more years, and any security updates will be released on those pages.

The previous version, MySQL 4.1, instead, will be retired completely. It has ended its extended period. As such, it will be removed from the download page, and also from the download archives. Next year, if you want …

[Read more]
MySQL 4.0 EOL

Extended support for MySQL 4.0 is about to be discontinued.

According to MySQL Lifecycle policy, MySQL 4.0 is now in extended support, meaning that only security and extremely severe bug fixes were applied to this release. The present condition ends on December 31, 2008. Then, MySQL 4.0 will join 3.23 in the list of unsupported versions.

The next version to meet the same fate will be 4.1, exactly one year later.

Spring cleaning in MySQL supported platforms

The MySQL Lifecycle Policy determines which versions are actively supported, and for which platforms such support applies.
The basic principle is that old versions are supported for a quite long, but definitely limited period, once they have been replaced by a newer GA version. For example, since the introduction of this policy, MySQL 3.23 and 4.0 have been retired.
The policy contains also provisions for a different kind of End of Life dismissal. When support for certain platforms has been discontinued by their vendors, of the platform is not widely used, MySQL reserves the right to stop building binaries and testing code on such obsolete platforms.
The reason is simple. While hardware can be bought and stored, time is a commodity in short supply, and there is only a given amount of time that our engineers can devote to testing and supporting multiple …

[Read more]
Showing entries 1 to 9