Difference between revisions of "MySQL Features & Bugs"

From ISoft Wiki
Jump to navigationJump to search
 
(10 intermediate revisions by 2 users not shown)
Line 1: Line 1:
* '''Automatic Initialization and Updating for TIMESTAMP and DATETIME''': added in 5.6.5. [https://dev.mysql.com/doc/refman/5.6/en/timestamp-initialization.html Source]
==Features==
* '''Automatic Initialization and Updating for TIMESTAMP and DATETIME''': added in 5.6.5 [https://dev.mysql.com/doc/refman/5.6/en/timestamp-initialization.html Source]
* '''Virtual/Generated Columns''': added in 5.7.9 [https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-9.html Source]
* '''JSON Column Data Type''': added in 5.7.8 JSON Data Type: [https://dev.mysql.com/doc/refman/5.7/en/json.html Source]
 
==Weird Bugs==
===DEFAULT NULL===
<source lang="mysql">
x INT DEFAULT NULL #works in all versions
x TIMESTAMP DEFAULT NULL #works in some versions, and not in others
x TIMESTAMP NULL DEFAULT NULL #seems to work in all?
</source>
This seems like a bug, but it changed between devdb and cloud (so between 5.7.15 and 5.7.24)
===LEFT JOINs act like JOINs sometimes when using ODBC date format===
This is [https://bugs.mysql.com/bug.php?id=69233 a bug in at least MySQL versions 5.6.10 - 5.6.21] that affects Crystal reports. 
<br>Reportedly, 5.5.31 is fine, and we know 5.6.22 and 5.7.6 have the bug fix (See Fogbugz {{case|13362}}).
 
https://bugs.mysql.com/bug.php?id=97067

Latest revision as of 14:41, 14 July 2022

Features

  • Automatic Initialization and Updating for TIMESTAMP and DATETIME: added in 5.6.5 Source
  • Virtual/Generated Columns: added in 5.7.9 Source
  • JSON Column Data Type: added in 5.7.8 JSON Data Type: Source

Weird Bugs

DEFAULT NULL

x INT DEFAULT NULL #works in all versions
x TIMESTAMP DEFAULT NULL #works in some versions, and not in others
x TIMESTAMP NULL DEFAULT NULL #seems to work in all?

This seems like a bug, but it changed between devdb and cloud (so between 5.7.15 and 5.7.24)

LEFT JOINs act like JOINs sometimes when using ODBC date format

This is a bug in at least MySQL versions 5.6.10 - 5.6.21 that affects Crystal reports.
Reportedly, 5.5.31 is fine, and we know 5.6.22 and 5.7.6 have the bug fix (See Fogbugz Case 13362).

https://bugs.mysql.com/bug.php?id=97067