>This sequence of events seems to break something.
>
>1) Create table foo
>2) create table bar
>3) create view foobar linking the two tables.
>4) drop table foo
>5) Create table foo (identical to first table)
>6) SELECT from view foobar.
>
>step six causes a relation not found error.
>
>Is this a bug? As long as the SQL statement that the view is based on is
>still valid why does it care if the table is dropped and recreated?
Sort of, but not the one you're thinking of.
Technically step 4 probably should have either prevented you from dropping
the table or automatically dropped the view based on whether you give
CASCADE or RESTRICT, however we don't currently support that notion
(hopefully 7.2 or so).
-----
SQL92 draft (11.18 <drop table statement>
4) If RESTRICT is specified, then T shall not be referenced in
the <query expression> of any view descriptor or the <search
condition> of any constraint descriptor.
Note: If CASCADE is specified, then such referencing objects
will be dropped by the execution of the <revoke statement> spec-
ified in the General Rules of this Subclause.