| From: | mlw <markw(at)mohawksoft(dot)com> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Don Baccus <dhogaza(at)pacifier(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Hackers List <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: SET variables |
| Date: | 2001-05-13 22:45:10 |
| Message-ID: | 3AFF0E76.7B0A3E92@mohawksoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian wrote:
>
> > In Oracle, temp tables occupy the same name space. One can not have two or more
> > users with the same temp table name without it being the same table. This is
> > why temp tables are not as used as one would think in Oracle.
> >
> > To use a temp table in Oracle you have to some up with some random naming
> > scheme. It really blows. Because of this Oracle developers have long stayed
> > away from temp tables.
>
> Wow, that really does stink. I know Informix can't have a temp table
> with the same name as a real table, and I thought that was bad, but
> Oracle is much worse.
>
Although....
One can see the advantage in a globally shared temporary table. For instance,
something like user web session management. One can insert and update against
the temp table and never have to worry about disk I/O or vacuuming. (Assuming a
temp table is implemented as a memory buffer)
--
42 was the answer, 49 was too soon.
------------------------
http://www.mohawksoft.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rainer Mager | 2001-05-13 22:55:38 | Postgres <-> Oracle |
| Previous Message | mlw | 2001-05-13 21:31:28 | Re: SET variables |