> I would far rather see people code explicit markers around statements
> whose failure can be ignored. That is, a script that needs this
> behavior ought to look like
>
> BEGIN;
> \begin_ignore_error
> DROP TABLE foo;
> \end_ignore_error
> CREATE ...
> ...
> COMMIT;
That seems awful noisy. Why not just:
BEGIN:
DROP TABLE foo;
ERROR: table foo does not exist;
CONTINUE;
etc....
Sincerely,
Joshua D. Drake
Command Prompt, Inc.