The 3.6.18 sqlite3.exe CLI produces the same problem: the internal
functions below can't be overloaded and trying to do so returns 5.
System is XP Pro x86 SP3.
What can I try next ?
>I see that sqlite3.dll is returning 5 == SQLITE_BUSY for the following
>functions:
>
>upper UTF-8
If I set a breakpoint on this:
rc = sqlite3_create_function(db, p->zName, p->nArg, p->enc,
p->pContext, p->xFunc, 0, 0);
I see that sqlite3.dll is returning 5 == SQLITE_BUSY for the following
functions:
upper UTF-8
lower UTF-8
like 2-arg UTF-8
like 3-arg UTF-8
Update: the problem is in the function registration.
I tried to comment out the UTF-16 registration and the really weird
thing is that using the following code, only GLOB with 3 arguments gets
actually registered (along with all 1-arg string functions and the two
collations).
There must be
Hi Pavel,
>I believe you need to show us your sql query. Maybe something in it
>forces SQLite to use UTF-16 version of the function.
Ummm, I don't kno where the problem is, but _any_ simple select will do
(for me), e.g.:
An UTF-8 base...
CREATE TABLE "PaysISO" (
"Nom_Iso" CHAR(43),
> I'm using the 3.6.18 Windows dll downloaded direct from the site.
>
> I just re-checked that.
I believe you need to show us your sql query. Maybe something in it
forces SQLite to use UTF-16 version of the function.
Pavel
On Mon, Oct 12, 2009 at 11:44 PM, Jean-Christophe Deschamps
Thank you for your fast answer.
>I'm surprised by this too. In fact, I cannot reproduce it.
I'm using the 3.6.18 Windows dll downloaded direct from the site.
I just re-checked that.
___
sqlite-users mailing list
sqlite-users@sqlite.org
I'm surprised that if I register overloading functions for LIKE or GLOB
in both UTF-8 and UTF-16, only the UTF-16 version is called despite the
fact that the database is UTF-8.
I don't see the same behavior with the other scalar functions (lower,
upper), which call the UTF-8 version as
7 matches
Mail list logo
