-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 15/12/11 15:52, Jaroslaw Staniek wrote:
> sqlite3_api is uninitialized, no reason it should be since I am not
> using redefined API functions.
It is initialized for dynamically loaded extensions. See this somewhat
dated page:
http://www.sqlite
On 14 December 2011 18:56, Roger Binns wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 14/12/11 09:34, Jaroslaw Staniek wrote:
>> But I did not consider using Statically Linked Extensions via
>> sqlite3_auto_extension.
>
> They aren't statically linked in the conventional sense.
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14/12/11 09:34, Jaroslaw Staniek wrote:
> But I did not consider using Statically Linked Extensions via
> sqlite3_auto_extension.
They aren't statically linked in the conventional sense.
> The issue arise from the fact that there is at least one
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Why are you posting to sqlite-dev? I don't see any relevancy.
SQLite does not have collations builtin. There is an API where you can
register whatever collations you want:
http://www.sqlite.org/c3ref/create_collation.html
There is another API wh
On 14 December 2011 18:13, Roger Binns wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Why are you posting to sqlite-dev? I don't see any relevancy.
>
> SQLite does not have collations builtin. There is an API where you can
> register whatever collations you want:
>
> http://www.sq
On 14 December 2011 17:49, Jaroslaw Staniek wrote:
> Some history: ICU lib was enabled in libsqlite3 on debian in 3.6.11-1
> [4] but then soon disabled in 3.6.14.2-1 because of packaging
> problems.
PS: It was exabled using SQLITE_ENABLE_ICU compile-time option
(http://www.sqlite.org/compile.htm
Hi,
Do you remeber this somewhat hot topic [1] about deploying SQLite?
Now I have hit the wall with unicode support in SQLite.
For databases sorting, matching (operator LIKE) and converting to
lower/upper case are all core features.
All this is related to so called collations.
At application level
