Tell us why you want temporary views, Philip. I've never even heard of
temporary views before, but I know that people - normally with a
different database background - have said they need temporary tables.
In some cases, they've been right and will have to wait for a new
Firebird version (I don't remember if it is part of Firebird 2.0 or
not), but in most cases they've been told how to do this in Firebird
without temporary tables.

Even though I've never tried creating and using a view within the same
transaction, it doesn't sound right to mix DDL and DML.

Looking forward to learn how temporary views may be useful,
Set

--- In firebird-support@yahoogroups.com, "unordained" wrote:
> 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