> This sounds kinda tempting to a lot of people, but it's not realistic.
If
> it
> persists longer than a session, then it's a real table! What would
> distinguish a real temp table from these persistent temp tables? Only
the
> "not logged" status? But if the data and table space is not going to
be
> cleaned up at process termination, then it implies a kind of
persistance
> that requires logging if the database is to recover properly.
>
> The magic of unlogged temp tables is that nothing in them is necessary
to
> perform fast recovery or log rollforward, therefore if the session is
> happy
> not to be able to rollback it's data modifications of an unlogged temp
> table, you can save performance and logging activity in the engine.
But
> this
> is not compatible with persistent tables.

As you point out it should not exist beyond a session. Basically I am
looking for all the characteristics of a temp table...except that I want
a permanent definition for the table to be stored in the system catalog.

sending to informix-list


sending to informix-list
sending to informix-list