Difference between revisions of "MySQL Features & Bugs"
From ISoft Wiki
Jump to navigationJump to search
| Line 13: | Line 13: | ||
This seems like a bug, but it changed between devdb and cloud (so between 5.7.15 and 5.7.24) | 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=== | ===LEFT JOINs act like JOINs sometimes when using ODBC date format=== | ||
This is [https://bugs.mysql.com/bug.php?id=69233 a bug in MySQL version 5.6.11] that affects Crystal reports. 5.6.10 and 5.6.12 are also affected. Reportedly, 5.5.31 is fine, and we know 5.6.20 is fine. | This is [https://bugs.mysql.com/bug.php?id=69233 a bug in MySQL version 5.6.11] that affects Crystal reports. | ||
Updating to 5.6.20 solves the issue (See Fogbugz case 13362). | <br>5.6.10 and 5.6.12 are also affected. Reportedly, 5.5.31 is fine, and we know 5.6.20 is fine. | ||
<br>Updating to 5.6.20 solves the issue (See Fogbugz case 13362). | |||
Revision as of 13:06, 23 January 2019
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 MySQL version 5.6.11 that affects Crystal reports.
5.6.10 and 5.6.12 are also affected. Reportedly, 5.5.31 is fine, and we know 5.6.20 is fine.
Updating to 5.6.20 solves the issue (See Fogbugz case 13362).
