On Sat, 31 Dec 2016 15:16:19 -0500 Paul Lambert <eb30...@gmail.com> 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. > I have observed that the file write mode of this function when using > the same file name a second time will delete the previous data in the > file. This is most likely accomplished by deleting the file and > recreating a new one. Better than guessing is strace(1). That would have shown you the exact syscall and parameters. > I believe this command needs to be modified so that it performs a > "stat" In general that's usually not the best approach. Any file operation inappropriate for a directory elicits EISDIR. Since there are many potential error conditions, it's better to simply operate on the name and handle any error, than to try to anticipate each one. --jkl _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
