In Linux systems (and in all Unix flavors) there is a /tmp directory or better, a /tmp file system. Anyone can create a file or directory in there and, in Linux, it cleared at boot time. (Other flavors use a cron job to clear out unused files.)
I propose a tmp database to be created with the other system databases an initialization time. It would have the following properties:
grant connect, resource to public
Not logged BUT ...
Can participate in any query, joined to any table in any database, regardless of the logging mode of that database.
Is emptied out after otherwise completing fast recovery
Why is it useful?
|Who would benefit from this IDEA?||As any user running a complicated sequence of queries that zip across databases and need a convenient way to pass data from one step to the next|
How should it work?
The closest I can come to a workaround is to:
But I have no nice workaround for the join issue. Perhaps create two such databases, tmp_wlog and tmp_nolog, to join in queries with logged or non-logged databases. I suppose all tables created in tmp_wlog would still be created WITH NO LOG, without the user having to specify this.
|Priority Justification||There are workarounds but it would be nice not to go through that rigmarole.|
|Customer Name||Jacob Salomon|