Re: [sqlite] .dump of utf16 database

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kevin Ryde wrote: > Or no doubt by querying it out, "sqlite3 old.db 'pragma encoding'". > But that's something .dump could helpfully do itself, could it? The SQLite shell can't read your mind :-) Adding something like this would require yet another

Re: [sqlite] .dump of utf16 database

Roger Binns writes: > > The only effect is what happens behind the scenes. I thought that might be so. > echo 'pragma encoding="UTF-16";' Or no doubt by querying it out, "sqlite3 old.db 'pragma encoding'". But that's something .dump could

Re: [sqlite] .dump of utf16 database

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kevin Ryde wrote: > Perhaps it doesn't matter to anything. The only effect is what happens behind the scenes. If you primarily use the - -16 interfaces to bind and retrieve text then the database also being utf16 means you avoid SQLite doing a

[sqlite] .dump of utf16 database

I was trying some .dump round-trips like sqlite3 old.db .dump | sqlite3 new.db and noticed if old.db is utf16, ie. pragma encoding=utf16, then new.db doesn't get that but instead is utf8. Is that intentional? Would slipping a pragma into the .dump output preserve the db coding? (I don't