[MDEV-8137] Surprising limit for varchar field for CONNECT database with ODBC Created: 2015-05-11 Updated: 2015-05-11 Resolved: 2015-05-11 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - Connect |
| Affects Version/s: | 10.0.17 |
| Fix Version/s: | 10.0.17 |
| Type: | Bug | Priority: | Major |
| Reporter: | Artur Formella | Assignee: | Olivier Bertrand |
| Resolution: | Not a Bug | Votes: | 0 |
| Labels: | ODBC, SQLITE | ||
| Environment: |
Windows 8.1, x64 |
||
| Attachments: |
|
| Description |
|
Varchar size in the following case is limited to 203. I don't know how to extend it.
And now:
But:
Throws an error: ENV:
SQLITE DDL:
|
| Comments |
| Comment by Olivier Bertrand [ 2015-05-11 ] | |
|
This not a bug but a limitation due to the fact that ODBC tables are not indexable. Look at the corresponding chapter of the documentation: In your case of a read only small table, the simpler way to make this work is to execute:
Why does it happen only when the varchar size is more than 203 is probably due to MariaDB that decides over this limit to use random access instead of sorting locally values obtained sequentially. |