[ODBC-288] Connector misses "interactive client" option Created: 2020-06-24 Updated: 2020-10-18 Resolved: 2020-10-18 |
|
| Status: | Closed |
| Project: | MariaDB Connector/ODBC |
| Component/s: | General |
| Affects Version/s: | 3.1.7 |
| Fix Version/s: | 3.1.10 |
| Type: | New Feature | Priority: | Major |
| Reporter: | Lawrin Novitsky | Assignee: | Lawrin Novitsky |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Description |
|
Such option would be useful for MSAccess/Excel/Foxpro or other application users. Or other option allowing to control server's wait timeout. |
| Comments |
| Comment by Anil Sharma [ 2020-06-26 ] |
|
when I try to send queries one by one in a loop MariaDB lost connection and it happened only with remote locations. |
| Comment by Lawrin Novitsky [ 2020-06-26 ] |
|
anilgenius Could you provide trace for this? strange, that it's only with remote servers. and if that was some read/write timeout, then myodbc would probably also have it. Unless they have longer default values. The other possible thing is some protocol misuse and commands go out of sync. But again, if it was so, that would also happened with local server. |
| Comment by Lawrin Novitsky [ 2020-06-26 ] |
|
anilgenius also, did it disconnect with compression turned on, or began when you turned it off, as I suggested? |
| Comment by Anil Sharma [ 2020-06-28 ] |
|
I need to retest. Becaz. it was working on high-speed internet but having an issue with slow network but on that slow network MS SQL Server was working fine. as on that project I moved to SQL express from MariaDB. i will test and send u the trace soon. |
| Comment by Lawrin Novitsky [ 2020-10-18 ] |
|
Commit db8c544(and some correction in the 2e0c5f3 |