> I don't know about SQLite2, but SQLite3 always expects strings in UTF-8 or
> UTF-16 (depending on what API function you use: those that want UTF-16
> usually have "16" somewhere in their names). If you have a string in some
> other encoding, you need to convert it to UTF-{8,16} before passing it to
> SQLite.
>
> However, if all your strings are pure 7-bit ASCII (and all your examples so
> far were such), then encoding shouldn't matter.
>
I believe so but I used PHP built in functions to do INSERTs. I did specify
any encoding explicitly but it's assumed to be UTF-8 by default.
>
> > they do in MySQL etc etc. In which case I could test different character
> > encoding to see what result I am getting in my tests.
>
> Can't you just retrieve the string exactly as SQLite reports it, and dump
> numeric values of each individual byte (which is what built-in hex()
> function does in SQLite3). Post the dump here, and we'll try to figure out
> the encoding.
> --
>
All right. I get it. I need to write something up to get the hex values of
strings in database. Get back to you soon with the dump. thanks.
Jason
_______________________________________________
sqlite-users mailing list
[email protected]
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
