Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
5.5.28a, 5.3.11, 5.2.13, 5.1.66
-
None
Description
psergey filed the upstream bug as http://bugs.mysql.com/bug.php?id=67507 over 2 months ago, but there has been no progress ever since, so maybe it's time to start doing something on our side, since 5.5.29 still has it and incompatible clients keep spreading.
According to MySQL manual, the syntax SET OPTION was deprecated (even although it doesn't seem to produce any warnings in 5.5), and now in 5.6 it's removed. However, even current versions of mysqldump 5.1-5.5 keep using it, which makes mysqldump < 5.6 incompatible with server 5.6 / 10.0.
I think we should at least replace SET OPTION with SET in mysqldump 5.3/5.5 (or maybe even 5.1..5.5) to stop producing potentially incompatible versions.
Additionally, please consider if we should prolong life of SET OPTION syntax in 10.x in order to let patched clients a chance to replace the old ones. (This part is not indicated in Affected/Fixed versions as it's just a suggestion for future).
Attachments
Issue Links
- links to
Activity
| Field | Original Value | New Value |
|---|---|---|
| Link | This issue relates to TODO-224 [ TODO-224 ] |
| Remote Link | This issue links to "Bug #67507 (Web Link)" [ 10100 ] |
| Description |
_Sergey Petrunia filed the upstream bug as http://bugs.mysql.com/bug.php?id=67507 over 2 months ago, but there has been no progress ever since, so maybe it's time to start doing something on our side, since 5.5.29 still has it and incompatible clients keep spreading._ According to MySQL manual, the syntax {{SET OPTION}} was deprecated (even although it doesn't seem to produce any warnings in 5.5), and now in 5.6 it's removed. However, even current versions of mysqldump 5.1-5.5 keep using it, which makes mysqldump < 5.6 incompatible with server 5.6 / 10.0. I think we should at least replace {{SET OPTION}} with {{SET}} in mysqldump 5.3/5.5 (or maybe even 5.1..5.5) to stop producing potentially incompatible versions. Additionally, please consider if we should prolong life of {{SET OPTION}} syntax in 10.x in order to let patched clients a chance to replace the old ones. (This part is not indicated in Affected/Fixed versions as it's just a suggestion for future). |
_[~psergey] filed the upstream bug as http://bugs.mysql.com/bug.php?id=67507 over 2 months ago, but there has been no progress ever since, so maybe it's time to start doing something on our side, since 5.5.29 still has it and incompatible clients keep spreading._ According to MySQL manual, the syntax {{SET OPTION}} was deprecated (even although it doesn't seem to produce any warnings in 5.5), and now in 5.6 it's removed. However, even current versions of mysqldump 5.1-5.5 keep using it, which makes mysqldump < 5.6 incompatible with server 5.6 / 10.0. I think we should at least replace {{SET OPTION}} with {{SET}} in mysqldump 5.3/5.5 (or maybe even 5.1..5.5) to stop producing potentially incompatible versions. Additionally, please consider if we should prolong life of {{SET OPTION}} syntax in 10.x in order to let patched clients a chance to replace the old ones. (This part is not indicated in Affected/Fixed versions as it's just a suggestion for future). |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Fix Version/s | 5.5.29 [ 12102 ] | |
| Fix Version/s | 5.2.14 [ 12101 ] | |
| Fix Version/s | 5.5.30 [ 11800 ] |
| Resolution | Fixed [ 1 ] | |
| Status | In Progress [ 3 ] | Closed [ 6 ] |
| Workflow | defaullt [ 25912 ] | MariaDB v2 [ 46447 ] |
| Workflow | MariaDB v2 [ 46447 ] | MariaDB v3 [ 67151 ] |
| Workflow | MariaDB v3 [ 67151 ] | MariaDB v4 [ 146335 ] |