One of the more frequently asked questions with MySQL 5.7 is “How can I upgrade my JSON data from using TEXT in an earlier version of MySQL to use the native JSON data type?”. Today I wanted to show an example of how to do so, using sample data from SF OpenData.…
Category Archives: Datatypes
Storing UUID Values in MySQL Tables
After seeing that several blogs discuss storage of UUID values into MySQL, and that this topic is recurrent on forums, I thought I would compile some sensible ideas I have seen, and also add a couple new ones.
See also follow up post called Mysql 8.0: UUID support , which explains the 8.0 solution.…
Getting Started With MySQL & JSON on Windows
MySQL is getting native support for JSON. This blog post will show you how to quickly get the MySQL server with these new features running on your Windows rig and how to write a small C# program in Visual Studio 2015 that stores a JSON document using the new native JSON data type.…
How to Easily Identify Tables With Temporal Types in Old Format!
The MySQL 5.6.4 release introduced support for fractional values within the temporal datatypes: TIME
, DATETIME
, and TIMESTAMP
. Hence the storage requirement and encoding differs for them in comparison to older (5.5 and earlier) temporal datatypes. The storage format for the temporal datatypes in the old format are not space efficient either, and recreating tables having both the new and old formats can be a long and tedious process.…
Upgrading old MySQL-5.5 format temporals to MySQL-5.6 format.
The temporal datatypes ‘TIME/DATETIME/TIMESTAMP’ supports fractional values starting from MySQL 5.6.4 version. Hence the storage requirement and encoding differs in comparison to pre- MySQL 5.6.4 temporal datatypes.
As mentioned in the section ‘Upgrading from MySQL 5.5 to 5.6’,
http://dev.mysql.com/doc/refman/5.6/en/upgrading-from-previous-series.html
Once you have imported the pre-MySQL 5.6.4 tables, ‘ALTER TABLE’ allows creation of tables containing temporal columns of both mysql-5.5 and mysql-5.6 format.…