There is very little pressure to keep the shell tool small. So the check for views which refer to non-existent tables could be put into there, as part of one of the dot-commands which do checking.
As for the code, it doesn't require anything more than SQL commands. There's no need for access to any SQLite internals. The code posted by Ryan Smith upthread is a good demonstration of how to manage that check without using SQLite internals. But if you distrust your schema so much that you want to sanity-checking VIEWs, you want to sanity-check TRIGGERs too, since they also have deferred entity-checking. And that is far more difficult. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
