.output means redirect from now henceforth until I change the output location.
.once means to redirect output for only the next command. Windows is not buffering, it is just not updating the directory entry. When you use .output the file is not closed until you either (a) redirect elsewhere or (b) end the program that opened the file. > -----Original Message----- > From: sqlite-users-bounces at mailinglists.sqlite.org [mailto:sqlite-users- > bounces at mailinglists.sqlite.org] On Behalf Of Richard Hipp > Sent: Sunday, 8 May, 2016 04:20 > To: SQLite mailing list > Subject: Re: [sqlite] output from sqlite3 .dump not going where I expected > > On 5/8/16, Jeremy Nicoll <jn.ml.sqlu.725 at letterboxes.org> wrote: > > I'm using Windows 8.1, 64bit, and yesterday installed the V3.12.02 > > > > I then tried eg > > > > .output myfile.txt > > .dump > > > > and was perplexed that no "myfile.txt" file was created anywhere obvious > > When I try this on my Win10 box, I see that the "myfile.txt" file is > created, but it remains empty until I either exist the sqlite3.exe > shell or enter something like ".output stdout" to redirect output > again. Apparently, Windows is buffering the output (50 MB of output > in my test case). I'm not sure what that is about, but redirecting > the output again seems to cure it. > > -- > D. Richard Hipp > drh at sqlite.org > _______________________________________________ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
