The solution presented even works, but is absurd.
Sqlite works well by default with ASCII and lets the user cope with other options. If you are going to use accent need other text encoding.
One hypothesis is to use the UTF-8 that people consider universal (there are controversies), but it has a problem, the code needed to handle correct UTF-8 is absurdly larger than Sqlite itself.
An alternative is to use UTF-16 (actually UCS-2) that will make the data size large. To implement a leotard suitable for this encoding will not be so simple either. There will be some performance gain, but I don’t know if it pays, most of the time it almost pays to use the solution of the question.
Sqlite says it supports both, of course it supports anything, but that doesn’t mean it has the leotard appropriate by default. Has an extension (ICU Extension), or you can use what the language offers, but rarely is this a viable option.
Another possibility is to use a Latin1 encoding (ISO 8859-1). It is much simpler, as fast as it can be where there are accents and does not take up extra space, but needs to turn with the extension, never seen a ready.
If you want to do something simpler, there’s a question here that I did and Bacco’s response solves the problem in 99% of the cases, for some people only those cases count.
Having said all this :P, the implementation of Sqlite in Android has the ability to do this, to work should use the option of COLLATE LOCALIZED
.
Did the answer solve the problem? Do you think you can accept one of them? See [tour] how to do this. You’d be helping the community by identifying the best solution. You can only accept one of them, but you can vote for anything on the entire site.
– Maniero