[MDEV-18102] CONNECT statement breaks connection and makes client unable to reconnect Created: 2018-12-29 Updated: 2018-12-29 Resolved: 2018-12-29 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Scripts & Clients |
| Affects Version/s: | 10.3 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Minor |
| Reporter: | Federico Razzoli | Assignee: | Unassigned |
| Resolution: | Not a Bug | Votes: | 0 |
| Labels: | client | ||
| Description |
|
CONNECT seems to be undocumented. This is something I ran on a MariaDB client by mistake, but still a crash is always supposed to be a bug.
|
| Comments |
| Comment by Elena Stepanova [ 2018-12-29 ] |
|
CONNECT (in this context) is a client command, not server. It is documented here: https://mariadb.com/kb/en/library/mysql-command-line-client/
So, in your case it attempts to reconnect to the db a on the host named b. Naturally, it can't, complains about the unknown host and the session can't work anymore, because it closed the previous connection and couldn't establish the new one. There is no crash, the server itself is okay. |
| Comment by Federico Razzoli [ 2018-12-29 ] |
|
But my point is about what happens after that. When I run SELECT 1, shouldn't it re-establish the former connection? That's what happens when mysql client loses the connection for any reason. |