Hello Peter,
I use UTF-8 exclusively in the engine parts my windows applications. I
just translate to UTF-16 for the GUI layer. In that way, no matter
what platform I support, the DB's remain the same.
C
Tuesday, May 5, 2015, 3:29:54 PM, you wrote:
PH> Thanks for all the replies. I'm still
On 5-5-2015 12:25, Clemens Ladisch wrote:
> Staffan Tylen wrote:
>> I must admit that I'm a bit confused here. If I'm not wrong UTF-8 differs
>> from ascii when the value is higher than '7f'x, but storing data in sqlite
>> as text with character values beteen 'x80'x and 'ff'x seems to be no
>>
On 5-5-2015 11:25, Kees Nuyt wrote:
> On Tue, 05 May 2015 10:50:00 +0200, Clemens Ladisch
> wrote:
>
>> Luuk wrote:
>>> on Windows 7:
>>> C:\temp>sqlite3.exe encoding.sqlite
>>> sqlite> select * from test;
>>> ??n
>>
>> The Windows console does not support UTF-8 with the default settings and
>>
Thanks for all the replies. I'm still confused on this. It sounds like
maybe UTF8 is the answer on OSX but UTF-16LE on Windows.
Whatever the answer to that, it seems there isn't a way to control the
encoding within sqlite3 so I guess I won't worry about it.
Pete
lcSQL Software
Staffan Tylen wrote:
> I must admit that I'm a bit confused here. If I'm not wrong UTF-8 differs
> from ascii when the value is higher than '7f'x, but storing data in sqlite
> as text with character values beteen 'x80'x and 'ff'x seems to be no
> problem. I previously thought that this could only
>
>
>>> I think it assumes UTF8 in both cases.
>>>
>>
>> when using '.dump', it does not create a UTF8 file on Windows 7 (sQlite
>> version 3.8.8.3)
>>
>
> It's UTF16-LE data.
>
>
>
I must admit that I'm a bit confused here. If I'm not wrong UTF-8 differs
from ascii when the value is higher than
On Tue, 05 May 2015 10:50:00 +0200, Clemens Ladisch
wrote:
>Luuk wrote:
>> on Windows 7:
>> C:\temp>sqlite3.exe encoding.sqlite
>> sqlite> select * from test;
>> ??n
>
>The Windows console does not support UTF-8 with the default settings and
>the C stdio functions. Any data you entered in the
Luuk wrote:
> on Windows 7:
> C:\temp>sqlite3.exe encoding.sqlite
> sqlite> select * from test;
> ??n
The Windows console does not support UTF-8 with the default settings and
the C stdio functions. Any data you entered in the console is not
encoded correctly.
Regards,
Clemens
At 09:22 05/05/2015, you wrote:
>On 4-5-2015 20:54, Richard Hipp wrote:
>>On 5/4/15, Peter Haworth wrote:
>>>When using the .dump command with .output to a filename, what
>>>encoding does
>>>sqlite3 for the file? Same as the database encoding? Is it possible to
>>>change whatever encoding
On 5-5-2015 09:22, Luuk wrote:
> On 4-5-2015 20:54, Richard Hipp wrote:
>> On 5/4/15, Peter Haworth wrote:
>>> When using the .dump command with .output to a filename, what
>>> encoding does
>>> sqlite3 for the file? Same as the database encoding? Is it possible to
>>> change whatever encoding
On 4-5-2015 20:54, Richard Hipp wrote:
> On 5/4/15, Peter Haworth wrote:
>> When using the .dump command with .output to a filename, what encoding does
>> sqlite3 for the file? Same as the database encoding? Is it possible to
>> change whatever encoding is used?
>>
>> Similarly, when using the
On 5/4/15, Peter Haworth wrote:
> When using the .dump command with .output to a filename, what encoding does
> sqlite3 for the file? Same as the database encoding? Is it possible to
> change whatever encoding is used?
>
> Similarly, when using the .import command, does sqlite3 assume the input
When using the .dump command with .output to a filename, what encoding does
sqlite3 for the file? Same as the database encoding? Is it possible to
change whatever encoding is used?
Similarly, when using the .import command, does sqlite3 assume the input
file is the same encoding as the database?
13 matches
Mail list logo
