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
 
  • Pages

    • About
    • Find and store the error return value in procedures or functions
  • Archives

    • August 2009
    • July 2009
    • June 2009
    • May 2009
    • April 2009
    • March 2009
    • February 2009
    • January 2009
    • December 2008
    • November 2008
    • October 2008
    • August 2008
    • July 2008
    • June 2008
    • May 2008
    • April 2008
  • Categories

    • MySQL 5.1 Features (3)
    • MySQL 5.4 New Features (2)
    • MySQL 6.0 New Features (5)
    • MySQL 6.x New Features (5)
    • News (8)
    • Personal Opinion (4)
    • Tiny Tweaks (10)
    • Uncategorized (19)



New Features In MySQL 6.x

« Progress Report March 2009
Globalization Tasks (Part 2 of 3) »

Globalization tasks (Part 1 of 3)

For today and tomorrow and the day after tomorrow, I (Peter Gulutzan) will say what the status is for “Globalization” tasks. These tasks meet Sun requirements for software; you could say that they’re moving forward due to Sun’s acquisition. I’ll give examples where the code is already working; for other cases I’ll just say what’s in the description in the worklog task.

WL#751 Error message construction
Current status: architecture review done
Version = 6.1
We’ll produce error messages taking into account the current character set and the user’s choice of language. Expect changes in errmsg.sys, errmsg.txt, internals documentation, string formatting, and @@character_set_results.

WL#897 Accept SQL statements written with UCS2, UTF16, UTF32
Status: not passed architecture review
Version = 6.x
Currently clients pass messages in UTF8, which can be converted to UCS2 or UTF16 or UTF32 by the server (it’s easy because Unicode character sets have the same repertoire). But let’s let clients pass messages in UCS2 or UTF16 or UTF32 from the start, possibly saving a conversion step.

WL#1287 REAL DIN-1 German collation
Status: not passed architecture review
Version = 6.x
Change handling of Sharp S when following DIN-1 (German dictionary) rules with certain character sets.

WL#1349 Use operating system localization to send it as a default client character set
Status: In code review
Version = 6.1
Thus utilities like ‘mysql’ will, instead of the compiled-in character set, try to figure it out via nl_langinfo, GetLocaleInfo, etc. I opposed this, but our support department thinks it will save them time.

Worklog WL#1820 Variant SJIS and UJIS Japanese Character Sets
Current status: not passed architecture review
Version = 6.1
Don’t be fooled into thinking that SJIS and UJIS always mean the same thing to everyone, there are several different encodings for yen sign, reverse solidus, overline and tilde. The weird but only practical solution is to add even more Japanese character sets, with differences only for those characters.

I’ll continue tomorrow.

This entry was posted on Wednesday, April 1st, 2009 at 8:50 pm and is filed under Uncategorized. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

Leave a Reply

New Features In MySQL 6.x is proudly powered by WordPress MU running on Blogs.mysql.com.
Entries (RSS) and Comments (RSS).