Re: [sqlite] Feature request: more robust handling of invalid UTF-16 data

*Richard:* the issue with the JSON extension seems unrelated to the issue that I reported originally, which relates to the SQLite C API (specifically, the sqlite3_bind_text16() and sqlite3_bind_text16() functions). My issue is still not fixed. I've expanded my original sample code to make it easie

[sqlite] Feature request: more robust handling of invalid UTF-16 data

In++); c += ((*zIn++)<<8); if( c>=0xD800 ){ int c2 = c=0xDC00 && c2<0xE000) { zIn += 2; c = (c2&0x03FF) + ((c&0x003F)<<10) + (((c&0x03C0)+0x0040)<<10); } else { c = 0xFFFD; } } } (And similarly for READ_UTF16BE.) Kind rega

Re: [sqlite] INSERT ... VALUES / want to "skip" default values

I'm surprised nobody mentioned that you can specify the columns to be inserted in the query: INSERT INTO test(a, c, d) VALUES (1, 2 3); (Note that `b` is missing it `a, c, d`. It will take the default value, which will be NULL, unless a different default was specified explicitly in the CREATE T