[ODBC-362] xpand compatibility: random error on connection Created: 2022-05-25 Updated: 2022-06-30 Resolved: 2022-05-27 |
|
| Status: | Closed |
| Project: | MariaDB Connector/ODBC |
| Component/s: | General |
| Affects Version/s: | 3.1.15 |
| Fix Version/s: | 3.1.16 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Diego Dupin | Assignee: | Lawrin Novitsky |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Attachments: |
trace4.txt
|
||||||||||||
| Issue Links: |
|
||||||||||||
| Description |
|
When connecting to xpand, even if xpand doesn't send CLIENT_SESSION_TRACK capability flag, ODBC execute command "SET session_track_schema= ON". Problem is that normally ODBC must not execute this : https://github.com/mariadb-corporation/mariadb-connector-odbc/blob/master/ma_connection.c#L967 odbc test server capability before issuing different command !? see wireshark attached file that confirm this. At the same time, a minor problem is that ODBC connector send capability to server that server has not advertise. It would be better not doing that. |
| Comments |
| Comment by Lawrin Novitsky [ 2022-05-26 ] |
|
As for the main session - I cannot think atm how cat that happen. And it happens randomly - puzzles even more. "At the same time, a minor problem is that ODBC connector send capability to server that server has not advertise. It would be better not doing that. " - I don't think that C/ODBC has anything to do with that. Must be C/C |
| Comment by Lawrin Novitsky [ 2022-05-27 ] |
|
What is even more strange, than random errors, is that as I read the code, and that was the intention, even if query setting session_track_schema value fails, the connector should just fall back to not using session tracking, but "normal" reading of current schema if it's requested by application. |
I am looking at the current repo code, and the change is not released yet, i.e. it is not in the 3.1.15