typo:
*I am summarizing options to support unicode* case-insensitive*:
On Sat, Oct 25, 2014 at 10:34 AM, dd wrote:
> I am summarizing options to support unicode case-sensitive:
>
> 1. Richard Hipp: icu ext
> 2. Aleksey Tulinov:
I am summarizing options to support unicode case-sensitive:
1. Richard Hipp: icu ext
2. Aleksey Tulinov: https://bitbucket.org/alekseyt/nunicode#markdown-
header-sqlite3-extension
3. Grey's suggestion: custom collation
Please add in options list if I missed.
I don't have experience in
On Fri, 24 Oct 2014 21:44:50 +0400
dd wrote:
> >>Convert everything to upper (or lower) case brute force.
>Sorry. I am not clear. Can you please elaborate this.
The standard function tolower(3) is locale-dependent. If your locale is
set to match the data's
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
On 24/10/14 20:44, dd wrote:
dd,
Any sample/open source avail to custom collation. Will it work for like
queries. Any performance degradation?
You might try nunicode:
https://bitbucket.org/alekseyt/nunicode#markdown-header-sqlite3-extension.
I think COLLATE NU700_NOCASE should do what
On Fri, Oct 24, 2014 at 1:44 PM, dd wrote:
> Hi,
>
> Any sample/open source avail to custom collation.
http://www.sqlite.org/compile.html#enable_icu
> Will it work for like
> queries.
Yes
> Any performance degradation?
>
Yes. Such is the price of unicode.
--
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
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
Hi,
ö and Ö same character but case different. I dont want to allow to insert
two entries for same data with different case. It works well with ascii
set. How to handle this? any inputs welcome.
$./sqlite3 '/home//sqlite/test/a.db'
SQLite version 3.8.7 2014-10-17 11:24:17
Enter ".help" for
9 matches
Mail list logo