| Bug #96839 | db.getSchema() returns no value after shell.setCurrentSchema() used | ||
|---|---|---|---|
| Submitted: | 11 Sep 2019 14:07 | Modified: | 2 Jul 2020 10:34 |
| Reporter: | Ryusuke Kajiyama | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | Shell General / Core Client | Severity: | S3 (Non-critical) |
| Version: | 8.0.20 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
[12 Sep 2019 7:58]
MySQL Verification Team
Hello Kajiyama-San, Thank you for the report and feedback. regards, Umesh
[15 Jun 2020 3:16]
Ryusuke Kajiyama
Not fixed yet in 8.0.20.
[2 Jul 2020 10:34]
Margaret Fisher
Posted by developer: Changelog entry added for MySQL Shell 8.0.22: MySQL Shell's db global object did not return the current schema when its properties were queried.

Description: Even if changing current schema with shell.setCurrentSchema(), db.getSchema() returns no value How to repeat: shell.setCurrentSchema("world_x"); db.schema() -- returns no value db.getTables() -- returns list of tables in world_x schema Also, Shell prompt does not properly show current schema in this case