Re: [sqlite] (dot) output call locks up when used on a named pipe

2017-01-01 Thread Rowan Worth
On 1 January 2017 at 08:55, James K. Lowden wrote: > On Sat, 31 Dec 2016 15:16:19 -0500 > Paul Lambert 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

Re: [sqlite] (dot) output call locks up when used on a named pipe

2016-12-31 Thread James K. Lowden
On Sat, 31 Dec 2016 15:16:19 -0500 Paul Lambert 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 >

Re: [sqlite] (dot) output call locks up when used on a named pipe

2016-12-31 Thread Richard Hipp
On 12/31/16, Paul Lambert wrote: > The "wb" your listing has add the "b" but based on what I have found > the "b" adds nothing and is the same as just "w." True for Linux. But SQLite is x-platform. And the "w" is significant on other systems. -- D. Richard Hipp

Re: [sqlite] (dot) output call locks up when used on a named pipe

2016-12-31 Thread Paul Lambert
I will need to do some testing. Here is an example of fopen using a named pipe mkfifo fifoname /* issue fopen for write end of the fifo */ wr_stream = fopen(fifoname,"w"); from:

Re: [sqlite] (dot) output call locks up when used on a named pipe

2016-12-31 Thread Richard Hipp
On 12/31/16, Paul Lambert wrote: > 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. if so then