I'm not going nuts, right?

If a transaction creates a view, it can't see the view (can't drop it, either)? But if it commits,
then that view is visible to new transactions, and if it rolls back, the view (that it can't see)
is dropped?

I have a use for temporary views (creating uniquely-named views on the fly that need to be visible
within the transaction, but will ultimately be dropped by the end of the transaction) ... I wasn't
planning on having to commit after every CREATE VIEW to make this work. (I -can-, but it feels
rather unsafe.)

-Philip