[ODBC-175] find from access in a varchar column is so slow ms access freezing for minutes in a small table. Created: 2018-08-25 Updated: 2021-03-04 |
|
| Status: | Stalled |
| Project: | MariaDB Connector/ODBC |
| Component/s: | General |
| Affects Version/s: | 3.0.6 |
| Fix Version/s: | 3.1 |
| Type: | Task | Priority: | Minor |
| Reporter: | Shimon Doodkin | Assignee: | Lawrin Novitsky |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Windows, MS Access |
||
| Description |
|
from ms access. also, there is another thing when tracing odbc , it says invalid length -1. many times sometimes. how to reproduce: CREATE TABLE `test` ( /* copy paste about 1000 times (select this line and next emmpty line and press control+c and hold control+v until there is enough line number): */ SELECT * FROM test; create empty ms access file. open the table in ms access and select the column with the text and press control+f. type something and click find. see it takes a long time. in a not very long table (i use MS Access 2013) |
| Comments |
| Comment by Lawrin Novitsky [ 2018-09-18 ] |
|
shimondoodkinAfter spending much time on trying to figure out what causes such a slow search with Access, I'd finally noticed that the table in your report has default charset utf8. That made me guess that the issue here is in redundant recoding work. |
| Comment by Shimon Doodkin [ 2018-09-19 ] |
|
did you have the slowness? |
| Comment by Lawrin Novitsky [ 2018-09-19 ] |
|
shimondoodkin yes, and setting connection charset to utf8 solved that |
| Comment by Shimon Doodkin [ 2018-09-25 ] |
|
setting charset to utf8 did not solve it for me. |
| Comment by Lawrin Novitsky [ 2018-09-25 ] |
|
Strange, for me it did solve. |