Ann W. Harrison said:

>
> The model of temporary tables that is being considered
> at the moment has them registered in RDB$RELATIONS et al,
> but visible (the tables themselves and the records in
> RDB$RELATIONS) only to the attachment/connection that created
> them.

So if I have an application that generates a temp table called 'stuff' and
two people are running this app, will I be creating two tables called
'stuff'?

I think that should be done at the client, in a temp file as I already do,
just to save confusion. What if the client disconnects poorly (like
Windoze crashing) and leaves these temp tables hanging about the DB?

> I suspect that works very very badly for tools that
> do connection pooling and those that use multiple connections.

There should be a way to view and manage temp tables if they are going to
be stored in DB space. :(

Personally, I don't even see the need for temp tables in an SQL database.
Sounds like a 4GL thing, like PROGRESS or something. =P

$0.02=>me;

--
Scott