Add some defenses to guard against case where a rule refers to a table
or view that's been dropped and then recreated with the same name (but, perhaps, different columns). Eventually we'd like to support this but for now all we can do is fail cleanly, rather than possibly coredumping if we proceed using the obsolete rule.
Showing
Please register or sign in to comment