By "brute force" I just meant specifying each conversion (such as Ö to
ö) individually. In my Tcl code, it is done with a single [string map
...] statement containing all of the conversions. The down side being,
as I mentioned earlier, that each time I run it on a new set of data I
have to check that a new accented character has not been added.
Gerry
On 10/24/2014 10:44 AM, dd wrote:
Hi,
Any sample/open source avail to custom collation. Will it work for like
queries. Any performance degradation?
Convert everything to upper (or lower) case brute force.
Sorry. I am not clear. Can you please elaborate this.
Thanks.
On Fri, Oct 24, 2014 at 9:16 PM, Gerry Snyder <mesmerizer...@gmail.com>
wrote:
In a vaguely similar situation I wrote a custom collation that converted
accented letters to their non-accented cousins. Since the conversion is on
a case-by-case basis I also had to do a pre-screening that would show any
non-ascii characters that I wasn't converting, so that I could add them to
my collation.
This is not quite what you want, since (I think) you want O and Ö and Ó to
be distinct, but the same sort of technique should work for you. Convert
everything to upper (or lower) case brute force. Perhaps tedious to set up,
but straightforward.
Gerry
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
