James K. Lowden wrote: >>> Why not use vis(3) instead? >> >> Because vis() is a nonstandard function that is not available >> everywhere, > > "everywhere" is a high standard, but vis is freely available and > included or packaged with almost anything not Windows.
It is not included in the distribution that I happen to use. >> and in any case it does not support SQL. > > Entirely irrelevant, as you surely know. What?!? The .dump output _is_ SQL, and is intended to be read again by SQLite, so whatever escaping mechanism it uses must be supported by SQLite itself. > To me, the most objectionable aspect of using char() is that the SQL is > munged. I see no reason to modify the user's text and introduce > further SQL interpretation. The INSERT statements _already_ are interpreted; that's the whole point of generating them in the first place. Regards, Clemens _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
