[ODBC-331] Verify if C/ODBC 3.1 could be based on C/C 3.2 Created: 2021-08-02 Updated: 2021-10-24 Resolved: 2021-09-27 |
|
| Status: | Closed |
| Project: | MariaDB Connector/ODBC |
| Component/s: | General |
| Affects Version/s: | None |
| Fix Version/s: | 3.1.14 |
| Type: | Task | Priority: | Blocker |
| Reporter: | Ralf Gebhardt | Assignee: | Lawrin Novitsky |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Description |
|
It needs to be verified if C/ODBC could also be based on C/C 3.2. We currently release C/ODBC and C/C with the same version numbers, one argument to stay with 3.1. But we still want to know if C/C .3.2 could be used. |
| Comments |
| Comment by Lawrin Novitsky [ 2021-08-11 ] |
|
Seemingly all is fine with C/C 3.2. Given Georg's notes on possible problems during the call, I've added setting charset to utf8mb3, if utf8 is requested by application. This should make the change in C/C invisible for C/ODBC users, and for next C/ODBC version that can be removed. Haven't pushed that yet, though. |