"Yes and yes."
:)
Alejo
On 10/26/06, Kees Nuyt <[EMAIL PROTECTED]> wrote:
Hi Richard,
On Thu, 26 Oct 2006 17:23:17 +, you wrote:
> So the question:
> Who will be adversely effected by the new error behavior
> in the sqlite command-line shell?
Not really. I prefer the new behaviour. At t
Hi Richard,
On Thu, 26 Oct 2006 17:23:17 +, you wrote:
> So the question:
> Who will be adversely effected by the new error behavior
> in the sqlite command-line shell?
Not really. I prefer the new behaviour. At the moment
I have to jump through hoops and scan my make logs to
detect errors
[EMAIL PROTECTED] writes:
> So the question: Who will be adversely effected by the new
> error behavior in the sqlite command-line shell? Who is
> using the sqlite command-line shell in scripts in such a
> way that the script will no longer work with the new
> behaviors? Do I need to change the
I don't use the command-line shell, but I'd definitely prefer not to see
a fundamental change in the behavior of any tool I use. The debugging
could get nasty and it's possible that someone using the tool in an
unsupervised script might not notice the problem until after it had done
some damage
In previous versions of SQLite, when the command-line shell
encountered an error, it would print an error message but
continue processing its input.
This seems wrong. In response to ticket #2045, I changed
the command-line shell so that when it is reading from a
file, it stops reading whenever
5 matches
Mail list logo
