On 2018-01-26, at 17:05, J Decker <d3c...@gmail.com> wrote: > On Fri, Jan 26, 2018 at 1:21 PM, Peter Da Silva < > peter.dasi...@flightaware.com> wrote: >> Sqlite uses NUL as the string terminator internally, the published API >> specifies has stuff like this all over the place:
>>> In those routines that have a fourth argument, its value is the number of >>> bytes in the parameter. To be clear: the value is the number of bytes in >>> the value, not the number of characters. If the fourth parameter to >>> sqlite3_bind_text() or sqlite3_bind_text16() is negative, then the length >>> of the string is the number of bytes UP TO THE FIRST ZERO TERMINATOR. > You stressed the wrong part there - *IS NEGATIVE* Why? Passing -1 as the length is a common way to tell sqlite3 to calculate the length itself. It's a documented and widely used part of the API. Therefore: >> It would be a huge push-up to change this, it would break everything, >> including extensions. I don't think it would be possible until something >> like sqlite4. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
