5.1.6 Coming

[peterlaursen]

MySQL 5.1.6 is being 'rolled out' to FTP-mirrors at this moment. The new EVENT feature will probably interest some! An there is also now a non-debug version for *nix (with reasonable performance, one must assume!). And there also now is a binary build for Windows with installer.

For for those who want to test it, you shold read the changelog http://dev.mysql.com/doc/refman/5.1/en/news-5-1-6.html. Note all the incompatible changes, new privileges' systems etc compared to 5.1.5.

I believe the simplest and most secure way to upgrade from 5.1.5 to 5.1.6 is to dump everything and import into an empty 5.1.6!

[peterlaursen]

From the changelogs (2 points):

1)

QUOTE

Partition support is not an “engine”, but it was included in the output of SHOW ENGINES. Now it is not. (Bug #14355) The have_partition_engine was renamed to have_partitioning. (Bug #16718)

One should think that thi issue would be fixed now http://www.webyog.com/forums/index.php?sho…mysql+5.1 .But this create statement seems to run forever on 5.1.6

CODE

CREATE TABLE employees (

   id INT NOT NULL,

   fname VARCHAR(30),

   lname VARCHAR(30),

   hired DATE NOT NULL DEFAULT '1970-01-01',

   separated DATE NOT NULL DEFAULT '9999-12-31',

   job_code INT,

   store_id INT

)

PARTITION BY LIST(store_id) (

   PARTITION pNorth VALUES IN (3,5,6,9,17),

   PARTITION pEast VALUES IN (1,2,10,11,19,20),

   PARTITION pWest VALUES IN (4,12,13,14,18),

   PARTITION pCentral VALUES IN (7,8,15,16)

);

So it is difficult to verify … 😡 However it is in accordance (copied from, actually) with the docs! And is the same in SQLyog, Query Browser and Command-line client. Without partitions there are no problems.

Now let's see if this http://bugs.mysql.com/bug.php?id=17331&thanks=4 is also 'not a bug' <_< 2)

QUOTE

ANALYZE TABLE is now supported for partitioned tables. (Bug #13441)

(since I am not able to create a partitioned table (on my windows installation – and I don't want to install this 5.1.6 on LINUX!) I can't verify it to work with SQLyog. Nevertheless I updated the FAQ accordingly!)

[peterlaursen]

One more issue with MySQL 5.1.6:

http://bugs.mysql.com/bug.php?id=17531&thanks=3&notify=131

[peterlaursen]

Now 5.1.7 is now out on FTP mirrors.

There is no installer-version for Windows this time. There also was quite a lot of bugs reported with the installer script for 5.1.6. Even 'Monty' himself reported a couple of bugs with it. I also seems that most MySQL developers had forgotten that there was such thing as Windows – they completely forgot to provide a Windows version of the mysql_upgrade program (that replaces the mysql_fix_privileges.sql script). On Windows you will have to run mysqlcheck with the new on_update option and next the mysql_fix_privileges.sql, if you want to use it with an existing /datadir. I recommend that you dump and reimport your databases.

There is now (again) max-versions of the servers in the package. Something is confused here! Looks like an internal communications problem in MySQL AB. Deep silence in the threads at bugs.mysql.com where users have asked for an explanation!

However the issues with previous versions with partitions (crash on querying INFORMATION_SCHEMA, VARIOUS deadlocks) and events-related privlege issues seems fixed. Events really work now!

And it is not an ALPHA anymore. It has been promoted to BETA. Seems fair enough for the server alone, but not for install- and maintenaince scripts and programs! They are EARLY ALPHA in my opinion! And further: User administration with 'MySQL Administrator' is completely broken (at least on my system). “user root@localhost may be deleted” it claims when trying to edit privileges. However I can log on as ROOT! I can create other users but cannot edit their privileges either.

But it works OK with SQLyog – even user administration does. Unfortunately it is not complete. But that gives us an opportunity to learn GRANT syntax … <_<

[peterlaursen]

Also note from the changelogs:

http://dev.mysql.com/doc/refman/5.1/en/news-5-1-7.html

QUOTE

Incompatible change: TYPE = engine_name is no longer accepted as a synonym for the ENGINE = engine_name table option. (TYPE has been deprecated since MySQL 4.0.)

This is implemented in SQLyog ver. 5.1 (beta) like this. It queries the MySQL version and uses KEYWORDS 'type' or 'engine' as appropriate. SQLyog versions before 5.1 alwasy use KEYWORD 'type'.

thus you will have to use SQLyog 5.1 to CREATE TABLE, ALTER TABLE, REORDER COLUMNS etc. with MySQL 5.1.7+

[peterlaursen]

FAQ write-up:

http://www.webyog.com/faq/32_80_en.html

[peterlaursen]

Forth and Back 😮

http://dev.mysql.com/doc/refman/5.1/en/news-5-1-8.html

QUOTE

In order not to break legacy applications, support for TYPE = engine_name has been restored, but now generates a warning.

Important: This option has been deprecated since MySQL 4.0. Beginning with MySQL 5.2, TYPE = engine_name will no longer be available and will produce a syntax error. You should not use TYPE in any new applications, and you should immediately begin conversion of existing applications to use the ENGINE = engine_name syntax instead. (Bug #17501)

FAQ write-up: http://www.webyog.com/faq/32_80_en.html

[peterlaursen]

They managed to get 5.1.9 out before the Users Conference.

Available from here for instance:

ftp://sunsite.dk/mirrors/mysql/Downloads/MySQL-5.1/

Still no installer for Windows. But everything seems to work like a dream. It will be FINAL this summer I guess. Quite impressive actually. And puts a little pressure on third-party vendors like Webyog <_<

[Author]

Posts