[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 behavior back to the > way it was and provide a command-line option to provoke the > new (more rational) behavior?
My use of the command line shell in scripts expects, in some cases, errors to be ignored and for the remainder of the queries to be processed regardless of the earlier errors. I agree that your proposed change would have been preferred as the original implementation. I wouldn't mind if the new behavior became the default as long as there was a new command-line option to enable backward-compatibility mode of ignoring errors and continuing to process. Cheers, Derrell ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
