[MDEV-10520] CONNECT TBL incorrectly applying default database to ODBC sub-table Created: 2016-08-08 Updated: 2016-10-28 Resolved: 2016-08-10 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - Connect |
| Affects Version/s: | 10.1.16 |
| Fix Version/s: | 10.1.17, 10.0.27 |
| Type: | Bug | Priority: | Major |
| Reporter: | Barry O' Neill | Assignee: | Olivier Bertrand |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | connect-engine | ||
| Environment: |
Windows Server 2012 |
||
| Description |
|
I have three tables. Two are CONNECT CSV tables coming from text files. The third is a CONNECT ODBC displaying data from a view on a sql server database. I can create a CONNECT TBL table and it works fine for the two csv type tables. However when I add the ODBC table to it things break down. The TBL table is created but when you attempt to select all from it, you are informed that the view cannot be found from the ODBC table. The reason the view cannot be found is that the TBL table is ignoring the server and database specified in the ODBC table and is instead forcing the default database onto the query. The view of course does not exist in the default local database. **The following works just fine:
**The following also works:
**If I create a TBL based on the two CSV tables it works fine:
**However as soon as I add the ODBC table to the mix, the select query fails and informs me that "dev.myView" does not exist. "dev" is the local db, it is ignoring the fact that the ODBC table has a differnt server and database "MyDatabase" specified:
I have tested every combination of options that I can think of but cannot get this to work, so I have come to the conclusion that it may be a bug. |
| Comments |
| Comment by Olivier Bertrand [ 2016-08-10 ] |
|
A bug indeed. |
| Comment by Barry O' Neill [ 2016-10-28 ] |
|
Just wanted to say thanks for fixing this. I have upgraded to 10.1.18 and all works fine. Thanks again. |