[MXS-3666] Unexpected internal state when a comment follows a SET statement Created: 2021-07-12 Updated: 2021-09-16 Resolved: 2021-08-16 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | Core |
| Affects Version/s: | 2.4.17 |
| Fix Version/s: | 2.5.0 |
| Type: | Bug | Priority: | Major |
| Reporter: | markus makela | Assignee: | markus makela |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | None | ||
| Description |
|
When a SQL statement contains a SET command followed by a comment that is separated by a semicolon, the server will respond with two packets. This confuses MaxScale as it expects only one response to the SET command. Version 2.5 and newer are not affected. This command reproduces the problem:
|
| Comments |
| Comment by markus makela [ 2021-08-16 ] |
|
Since this is fixed in 2.5 and it's not simple to fix in 2.4, I'll close this as Fixed in 2.5.0. |