-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 09/26/2011 03:31 PM, David Garfield wrote: > And I suppose the alternative to fixing them in SQLite is to > document them.
Ticket created where the team can give their official response and people can be pointed the next time this comes up: http://www.sqlite.org/src/info/57c971fc74 > On the other hand, the existing behavior means that > some unexpected things are broken. [ shell .dump stops at NUL too] Yet another illustration of the shell being a developer tool rather than a rock solid part of SQLite. Incidentally if you use the shell I include with APSW it will detect the NULs and generate correct dump output although it only works if the database is in UTF8 encoding. > An alternative variant might be to enforce that NUL cannot occur in > text (i.e. makes it error out). That would definitely break existing usage. > One interesting thought: It might actually make the functions faster > to not have to count the length of strings. I doubt it has a measurable effect overall (Amdahl's Law). Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk6BBwsACgkQmOOfHg372QRKtQCfXS3pvelZQOXwhedzyEjNI6TY +j8AmgOy18GBM8YF5SuSgYA2mKjWs2f4 =vptL -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
