But you can rename the tables to something more meaningful.In an import operation, Access never overwrites a table in the database.In fact, the command type is not needed by view rules, but the result relation may affect the way in which the query rewriter works, because special care needs to be taken if the result relation is a view.
These entries don't participate directly in the query, since they aren't referenced by the subquery's join tree or target list.
These rules will rewrite the command, typically into a command that updates one or more tables, rather than views. Note that rules are evaluated first, rewriting the original query before it is planned and executed.
Therefore, if a view has triggers for the view, and the rewriter cannot automatically rewrite the query as an update on the underlying base relation, an error will be thrown because the executor cannot update a view as such.
The rewriter uses them to store the access privilege check information that was originally present in the range-table entry that referenced the view.
In this way, the executor will still check that the user has proper privileges to access the view, even though there's no direct use of the view in the rewritten query. The rule system will continue checking the remaining range-table entries in the top query (in this example there are no more), and it will recursively check the range-table entries in the added subquery to see if any of them reference views.