Planet MySQL Planet MySQL: Meta Deutsch Español Français Italiano 日本語 Русский Português 中文
Showing entries 1 to 9

Displaying posts with tag: deprecation (reset)

SF MySQL Meetup Presentation: Changes in MySQL 5.7
+4 Vote Up -0Vote Down

Last Wednesday, I spoke at the San Francisco MySQL Meetup on the topic of changes coming in MySQL 5.7 (and later).  We actually went through two different slide decks; the first on features being considered for deprecation in MySQL 5.7 (or later), and the second set providing a brief overview of the new features and benefits already introduced in MySQL 5.7 via the development milestone releases (DMRs) published to date.  A big thanks to the entire SF Meetup group, and in particular the organizers (Erin, Mike and Darren), for having me.  The event was streamed and recorded, and you can view the …

  [Read more...]
Spring Cleaning: Useless protocol commands
+2 Vote Up -0Vote Down

In an earlier post, I commented on clients and utility programs which seem to no longer be useful, and opened (or referenced existing) public bug reports to deprecate and remove, where appropriate.  That effort came actually was the product of a different initiative:  I was looking for clients which might leverage the full spectrum of MySQL protocol commands in an effort to understand whether certain protocol commands are in use.  …

  [Read more...]
Option prefixes deprecated
+0 Vote Up -0Vote Down

MySQL 5.6.13 was released earlier this week, and in that release (as well as 5.5.33) the ability to use unique option prefixes was deprecated.  This is fully removed from MySQL 5.7, and I thought it might be useful to amplify the change log notes on why this was done:

Previously, program options could be specified in full or as any unambiguous prefix. For example, the …

  [Read more...]
Spring cleaning: Useless clients and programs
+2 Vote Up -0Vote Down

Stewart Smith recently questioned the current relevance of the MERGE storage engine, and it prompted me to finish a similar recent exercise I’ve been thinking about related to MySQL clients (UPDATE: and programs).  This originally came up when I listed the contents of the MySQL bin directory:

D:\mysql-advanced-5.6.11-win32>dir bin\*.exe
Volume in drive D is Data
Volume Serial Number is 4015-B2FF

Directory of D:\mysql-advanced-5.6.11-win32\bin

04/05/2013  06:52 …

  [Read more...]
Deprecated in MySQL 5.6 – ignore_builtin_innodb
+0 Vote Up -0Vote Down

Back when MySQL 5.1 was first released, Oracle (which didn’t at the time own Sun or MySQL) wanted to add new InnoDB functionality faster than MySQL could effectively incorporate it into the server, and the InnoDB plugin was introduced.  It provided 5.1 users the option of deploying a more advanced version of InnoDB, or using the more conservative built-in version baked into MySQL.  By the time the plugin reached GA status, though, Oracle had announced the acquisition of Sun (and MySQL), and things started to change.  The coordination between the InnoDB development team at Oracle and the MySQL development team increased once …

  [Read more...]
Deprecated in MySQL 5.6 – YEAR(2)
+5 Vote Up -0Vote Down

Back in April, I issued a challenge to identify any compelling use case for the YEAR(2) data type.  Months later, I still don’t have such a use case, and the release of 5.6.6 brings deprecation of support for the YEAR(2) datatype.  Trying to create a table with a YEAR(2) column in 5.6.6 or greater will result in conversion to YEAR(4) and a warning:

| 5.6.6-m9  |
1 row in set (0.00 sec)

mysql> CREATE TABLE y (y YEAR(2));
Query OK, 0 rows affected, 1 warning (0.13 …
  [Read more...]
Why your pre-4.1 client won’t like MySQL 5.6
+0 Vote Up -0Vote Down

I have to think that the “Client does not support authentication protocol” error message may be the single most common error ever encountered for MySQL. While it’s not exactly coming back in 5.6, those users who have implemented workarounds in support of older client libraries will find they need to add an additional step if they upgrade to 5.6. This is because in 5.6.5, a change was made to default the secure_auth option to ON. Here’s what the manual has to say about this:

This option causes the server to block …

  [Read more...]
A Critical Warning If You Are Using InnoDB Hot Backup
+0 Vote Up -0Vote Down

If you are using InnoDB Hot Backup and a recent version of mysqld (at least 5.0.67 or higher, including 5.1.30, though it may be later versions), your backup will run fine and output OK! at the end, as it should.

Except for one thing.

The binary log file and position do not appear in their rightful place. Here’s a snippet of the output from the backup:

innobackup: MySQL binlog position: filename 'Warning', position (Code 1287):
'TYPE=storage_engine' is deprecated; use 'ENGINE=storage_engine' instead
090210 03:55:04  innobackup: innobackup completed OK!

That’s pretty misleading — looks like the backup …

  [Read more...]
Recommendation to my fellow F/OSS developers
+0 Vote Up -0Vote Down

I temporarily withdraw my recommendation until the intentions of Oracle become less cloudy...

Hash: SHA1

Allow me to make a recommendation to my fellow Free Software
developers.  Oracle Corporation's recent business practices show
aggression toward the Free/Open Source Software community, and their
database couldn't be confused with Free software if one had allergies
and a blindfold on.

Therefore, I recommend to my compatriots in the F/OSS community the
deprecation of oracle as a database back end to our software.  I am not
necessarily suggesting that software currently providing compatibility
with the database remove the existing support; …

  [Read more...]
Showing entries 1 to 9

Planet MySQL © 1995, 2016, Oracle Corporation and/or its affiliates   Legal Policies | Your Privacy Rights | Terms of Use

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.