Bug #84154 | ERROR REFRESHING IMPORTED DATA FROM DIFFERENT SCHEMAS IN SAME CONNECTION | ||
---|---|---|---|
Submitted: | 9 Dec 2016 23:40 | Modified: | 5 May 2017 22:10 |
Reporter: | Javier Treviño | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL for Windows: MySQL for Excel | Severity: | S2 (Serious) |
Version: | 1.3.6 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[9 Dec 2016 23:40]
Javier Treviño
[10 Dec 2016 1:52]
Javier Treviño
Posted by developer: Fixed the way the current schema is assigned to the connection being used to refresh imported data. Connections for imported data are first checked to see if they are already connected, otherwise a connection is attempted; if successful the current schema is assigned to the connection. That way we ensure a shared connection for different imported tables switches to the current schema correctly.
[5 May 2017 21:47]
Rafael Antonio Bedoy Torres
Posted by developer: Fixed on 1.3.7 build 2
[5 May 2017 22:10]
Christine Cole
Posted by developer: Fixed as of the upcoming MySQL for Excel 1.3.7 release, and here's the changelog entry: A mismatch between the current schema and the current connection caused the refresh action to fail when a worksheet with imported data was created as an Excel table, saved, closed, and then reopened. Thank you for the bug report.