Roger, hadn't considered that. I was using .echo on, to see the contents of the tmp.txt file on the screen. Under v3.3.6 it showed me everything on screen INCLUDING the sql command being used, and the file simply contained the results. Now the current release shows me the contents of the tmp.txt up to and including the .output statement, doesn't show the sql command, but places that command within the file, right on the top.
Tried .echo off, and it stops the sql command going into the file which is what I need, but now I don't see the contents of the tmp.txt as it runs. Not a big deal, just a strange difference between release levels. Thanks for the reply. Rick Timms ________________________________ From: Roger Binns <rog...@rogerbinns.com> To: sqlite-users@sqlite.org Sent: Thursday, November 17, 2011 10:14 PM Subject: Re: [sqlite] Suppression of SQL Command when routing Output to File -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 17/11/11 20:00, Richard Timms wrote: > .echo on [...] > Now I get that, plus the actual sql statement itself. How do I suppress > the sql statement from appearing on the file? I don't understand your question. You turned echo on so you get the sql statements printed. If you don't want them printed then don't turn it on. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk7F26wACgkQmOOfHg372QTDUACg2QE3F0Xu/OccdHFn/iLb/qe8 TU0AoMMKCXG8db0rVzqptKU1OOACbqJ/ =+2pW -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
