Richard, J Decker,
Just to close this down.
The command was
select * from device;
We used .quit and Ctrl-D to exit the shell
The command sequence was as simple as
sqlite3 DATABASE.sqlite
We knew about things like less and head and so we avoided them.
The version of Sqlite seems to be the problem, the standard one with
Ubuntu 14.04 LTS is 3.8.2 which we know is old, but until now seems to
have been fine.
Upgrading our production servers to Ubuntu 16 LTS is a massive
undertaking. We have nine of them with test and preprod so upgrading and
testing everything again is many, many weeks work :(
We've upgraded Sqlite CLI to the latest 3.18.0 and are trying this out
in a nice safe environment.
Thanks
Rob
On 15 May 2017, at 12:38, Richard Hipp wrote:
On 5/15/17, Richard Hipp <d...@sqlite.org> wrote:
On 5/15/17, Rob Willett <rob.sql...@robertwillett.com> wrote:
As part of the testing we noticed that -shm and -wal files were
being
left after we used sqlite3 on the command line. This puzzled us as
we
didn't see any errors in our test scripts.
How is the command being ended. Are you inserting a ".quit" command?
Are you somehow causing the shell to terminate prematurely, perhaps
by
piping the output into a filter (such as "head") that closes the
input
connection early? What version of the SQLite shell is running? What
is the query?
Never mind - it appears that JDecker already knew the problem and the
solution....
--
D. Richard Hipp
d...@sqlite.org
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
