Re: Trigger name missing

Simon Slavin <[email protected]> Sat, 7 Mar 2020 17:06:16 +0000
Newsgroups gmane.comp.db.sqlite.general
Message-ID <[email protected]>
On 7 Mar 2020, at 4:49pm, John G <[email protected]> wrote:

> Would it be possible to create an SQL verification program, which just like 'sqlite3_analyzer' and 'sqldiff' could be run separately?
> It could *warn* about apparently incompletely defined triggers and other possible pitfalls.

The shell tool has this ability, by executing the following PRAGMAs:

<https://sqlite.org/pragma.html#pragma_cell_size_check>
<https://sqlite.org/pragma.html#pragma_integrity_check>
<https://sqlite.org/pragma.html#pragma_foreign_key_check>

Used in the above order it will spot several kinds of corruption.  It can be scripted from your OS command-line shell:

<https://sqlite.org/cli.html#using_sqlite3_in_a_shell_script>
_______________________________________________
sqlite-users mailing list
[email protected]
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users