On 5-5-2015 09:22, Luuk wrote: > On 4-5-2015 20:54, Richard Hipp wrote: >> On 5/4/15, Peter Haworth <pete at lcsql.com> 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 >>> file is the same encoding as the database? >>> >> >> 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)
or am i doing something wrong? on Windows 7: C:\temp>sqlite3.exe encoding.sqlite SQLite version 3.8.8.3 2015-02-25 13:29:11 Enter ".help" for usage hints. sqlite> select * from test; een ??n sqlite> .dump PRAGMA foreign_keys=OFF; BEGIN TRANSACTION; CREATE TABLE test (x varchar(20)); INSERT INTO "test" VALUES('een'); INSERT INTO "test" VALUES('??n'); COMMIT; sqlite> select x, length(x), hex(x) from test; een|3|65656E ??n|3|82826E sqlite> PRAGMA encoding; UTF-8 sqlite> The '82' is not a UTF-8 representation of the '?' (length=3 is correct)