[bug] Database is not set after a reconnect

[scottnemes]

Currently when your connection is lost and a reconnect occurs, mycli thinks you are still connected to a database, while the connection itself does not:

MySQL scottn@localhost:(none)> use dev;
You are now connected to database "dev" as user "scottn"
Time: 0.001s
MySQL scottn@localhost:dev> select * from t2;
+----+
| id |
+----+
| 2  |
| 2  |
+----+

2 rows in set
Time: 0.004s
MySQL scottn@localhost:dev> select * from t2;
Reconnecting...
Reconnected successfully.
Any session state was reset.
(1046, 'No database selected')
MySQL scottn@localhost:dev>

This should be fixable by using the connection.select_db() method after the connection.ping(reconnect=True) is sent.

[scottnemes]

I will get this fixed and update tests accordingly.

[onosendi]

I just came to report this as well. Here's my log if this helps.

Reconnecting...
Reconnected successfully.
Any session state was reset.
(1046, 'No database selected')
foo@bar:foo> show tables;
(1046, 'No database selected')
foo@bar:foo> use foo;
You are already connected to database "foo" as user "foo"
Time: 0.000s
foo@bar:foo> show tables;
(1046, 'No database selected')

[rolandwalker]

Fixed in release https://github.com/dbcli/mycli/releases/tag/v1.44.2 . Thanks @scottnemes !