"Da Martian" <[EMAIL PROTECTED]> wrote: > When using the > NON16 version of prepare: > If I add text which is in UTF16 what happens? > > 16 Version: > If I add UTF16 text what happnes? > if I add UTF-8 Text what happens? > if I add ASCIII text what happnes? >
You seem really confused about the whole encoding issue. Unless you take specific actions to make it otherwise, SQLite stores all text internally as UTF-8. I assume that is what you are doing, but it really does not matter because the API works exactly the same regardless of how SQLite stores the text internally. All text inputs to SQLite are expected to be UTF-8, or in the case of sqlite3...16() routines, UTF-16. No exceptions. SQLite never accepts text encoded using a microsoft codepage. If you send UTF-16 or some goofy microsoft codepage to an SQLite API that expects UTF-8, then you will end up with chaos. If you send UTF-8 or a codepage into one of the sqlite3...16() APIs, then you will end up with chaos. Don't do these things. Hand most SQLite APIs UTF-8 text. Send the SQLite APIs that end in "16" UTF-16 text. Do any format conversions ahead of time. If you just follow those simple rules, everything will work. -- D. Richard Hipp <[EMAIL PROTECTED]> ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
