Simon, As I just wrote to Richard Hipp, I must not have the .once command, but see my reply for a possible solution using .timeout and tell me what you think. I'm not sure what the -cmd really does. It is not described in my man page.
--Mark -----Original Message----- > From: Simon Slavin <slavins at bigfraud.org> > Date: Mon, 25 Apr 2016 14:12:27 +0100 > To: SQLite mailing list <sqlite-users at mailinglists.sqlite.org> > Subject: Re: [sqlite] sqlite3 command line, read-only > > On 25 Apr 2016, at 2:00pm, Mark Foley <mfoley at novatec-inc.com> wrote: > > > problem is that the PRAGMA > > statement echo the timeout value to stdout: > > > > sqlite3 "mydbpath" \ > > "PRAGMA busy_timeout=5000;select distinct value from cal_properties where > > key = 'CATEGORIES'" > > 5000 > > Orange Category > > Green Category > > Blue Category > > Purple Category > > Blue Category,Holidays > > Personal > > > > I'd have to do some major editing to my queries to reject the 1st row make > > the > > query processing very depending on whether or no I use the PRAGMA. Is there > > a > > way to surpress the PRAGMA output? > > Hmm. I don't know whether this might work: > > .once dummy.txt;PRAGMA busy_timeout=5000;select distinct value from > cal_properties where key = 'CATEGORIES' > > This might route the result of the PRAGMA to your dummy.txt file, which you > can ignore. You might have to specify a writable directory. Or you could > try sending it to /dev/null or whatever your OS supports as "throw this away". > > Simon. > _______________________________________________ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users >
