>From: Jens Miltner
>Sent: Wed, February 3, 2010 9:46:06 AM
>Just another thought to consider: depending on the amount of non-ASCII
>(or non-roman) string data stored in your database, in may be more
>efficient to use UTF-8 encoding rather than UTF-16 encoding:
>UTF-8 takes up less space for
Am 01.02.2010 um 00:02 schrieb a1rex:
> I am planning to store text in a database which has to accommodate a
> few international languages.
> In this case I have to use UTF-16LE encoding for my TEXT fields.
> I know that once an encoding has been set for a database, it cannot
> be changed.
J
Thank you for your help!
This call:
sqlite3_exec(handle,"PRAGMA encoding = \"UTF-16\"",NULL,NULL,&zErr);
works.
Samuel
- Original Message
From: Igor Tandetnik
To: sqlite-users@sqlite.org
Sent: Sun, January 31, 2010 6:12:27 PM
Subject: Re: [sqlite] UTF-8 and
On Sun, 31 Jan 2010 18:12:27 -0500, "Igor Tandetnik"
wrote:
>It's PRAGMA encoding = "UTF-16". The parameter needs to be quoted.
This is indeed the syntax description. Peculiarly, anywhere
else, string literals have to be single quoted.
Is this something to iron out in v4 ?
--
( Kees Nuyt
a1rex wrote:
> I am planning to store text in a database which has to accommodate a few
> international languages.
> In this case I have to use UTF-16LE encoding for my TEXT fields.
Perhaps there are some external reasons, but there's nothing in SQLite that
would force this. For example, UTF-8 i
I am planning to store text in a database which has to accommodate a few
international languages.
In this case I have to use UTF-16LE encoding for my TEXT fields.
I know that once an encoding has been set for a database, it cannot be changed.
Do BLOBS are effected?
I guess I cannot mix TEX
6 matches
Mail list logo