J Decker wrote: >> *If any NUL characters occur at byte| offsets less than the value of the >> fourth parameter then the resulting| string value will contain embedded >> NULs.* > > So it's best used as data, and not keys > and I see unless custom aggregate()s or function()s ...
If you want embedded NULs, use blobs. > insert into ? (?,?) values(?,?) > with bind ( 'ta\0le', '\0','\1', 'hello\0','\0world' ) > > bad things happen :) but what if I ? In this case, the bad thing that happens is a syntax error; you cannot use parameters for table/column names. And SQL statements cannot contain embedded NULs; parsing stops at the detected end of the string. Regards, Clemens _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
