"Yes and yes." :) Alejo
On 10/26/06, Kees Nuyt <[EMAIL PROTECTED]> wrote:
Hi Richard, On Thu, 26 Oct 2006 17:23:17 +0000, 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 and signal them. > 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? It might break some of my scripts, but rightly so. I'll be glad to repair them. > Do I need to change the behavior back to the way it was > and provide a command-line option to provoke the new > (more rational) behavior? Not really needed, but it would be nice to have a choice to explicitly suppress errors or explicitly provoke the new behaviour, either way. As my makefiles use a macro $(SQLITE) instead of the program name itself it is easy to add any switch anyway. Your approach in the remarks of said ticket is right, in my view. Thank you for any abort-on-error solution and the beautiful, consistent product sqlite is!
----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
