On 1 January 2017 at 08:55, James K. Lowden <[email protected]> wrote:
> On Sat, 31 Dec 2016 15:16:19 -0500 > Paul Lambert <[email protected]> wrote: > > > I have used the (dot) .output call in conjunction with a both a file > > and name pipe on Linux with Sqlite 3.13 installed. With a file this > > functions successfully and completes. When using a named pipe this > > functions locks up sqlite and it must be aborted for termination. > > Is something draining the pipe? If not, SQLite will naturally block > when the pipe fills. > Yeah, this. Even *opening* a named pipe for writing blocks until a reader shows up (in linux at least). You can easily observe this behaviour: $ mkfifo /tmp/fifo $ echo hello > /tmp/fifo Notice that you don't get the prompt back immediately like you normally would when running echo. But if you open another terminal and do: $ cat /tmp/fifo You'll see "hello" in the new terminal and get the prompt back in your first terminal. In my testing this is consistent with the behaviour of sqlite3's .output command. -Rowan _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
