Roman. That's a good one. It affects the command status of well formed SQL as well:
sqlite-src-3230000/bld$ echo 'SELECT * FROM sqlite_monster' | ./sqlite3;echo $? Error: near line 1: no such table: sqlite_monster 0 sqlite-src-3230000/bld$ echo 'SELECT * FROM sqlite_monster;' | ./sqlite3;echo $? Error: near line 1: no such table: sqlite_monster 1 Piped SQL lacking a trailing semicolon does indeed cause the shell to report the wrong last command status. Peter On Wed, Apr 4, 2018 at 4:46 PM, Roman Fleysher < roman.fleys...@einstein.yu.edu> wrote: > Dear SQLiters, > > > I am using sqlite3 shell from bash scripts and I stumbled on what I think > is incorrect exit code on error. In the first scenario, on error the exit > code is 1 -- expected, in the second it is 0 -- unexpected. The error > message is the same in both. Is that normal? > > > echo -e "ww; \n.exit" | sqlite3 > > Error: near line 1: near "ww": syntax error > > echo $? > > 1 > > > echo -e "ww" | sqlite3 > > Error: near line 1: near "ww": syntax error > > echo $? > > 0 > > Thank you, > > Roman > > _______________________________________________ > 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
