Re: Self-referencing table question

From: Edmund Bacon <ebacon(at)onesystem(dot)com>
To: Sean Davis <sdavis2(at)mail(dot)nih(dot)gov>
Cc: PostgreSQL SQL <pgsql-sql(at)postgresql(dot)org>
Subject: Re: Self-referencing table question
Date: 2005-03-24 19:37:16
Message-ID: 424316EC.2090207@onesystem.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

Sean Davis wrote:

> Nice. Thanks for doing my work for me!

Yeah, well put it down to a certain amount of curiosity and a slack
period at work ...

> I guess I will have to think about it more seriously.
>
> It could be a slight bit complicated because my code is running under
> mod_perl, so connections are cached. As I understand it, the temp
> table will stick around, so I will have to be careful to explicitly
> drop it if I don't want it to persist?

I'm guessing so. However you could put everything in a transaction
and use CREATE TEMP TABLE ... ON COMMIT DROP, and use INSERT INTO rather
than SELECT INTO. The speed should be about equivalent - but you'd have
to test to make sure.

> Also each table will need a unique name (I have a session_id I can
> use), as it is possible that multiple temp tables will exist and be
> visible to each other?

Each session (connection in your case?) has it's own temporary table
space, so you shouldn't have to worry about that.

>
>
> Thanks again,
> Sean
>

--
Edmund Bacon <ebacon(at)onesystem(dot)com>

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Moran.Michael 2005-03-24 20:22:34 Re: Funtions + plpgsql + contrib/pgcrypto = ??
Previous Message Sean Davis 2005-03-24 19:01:13 Re: Self-referencing table question