From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Kenneth Tilton <kentilton(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: nooby Q: temp tables good for web apps? |
Date: | 2009-04-08 02:13:35 |
Message-ID: | dcc563d10904071913rd68f4f2vc102d4327fb7d871@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Apr 7, 2009 at 7:12 PM, Kenneth Tilton <kentilton(at)gmail(dot)com> wrote:
>
>
> Scott Marlowe wrote:
>>
>> You can use a different method if you need a table available to the
>> same session. Create a schema based on the session id, and put your
>> temp tables there, only don't call them temp tables. You'll either
>> need to make sure you always clean up your temp schema your session
>> created or come up with a daemon that comes along every hour or so and
>> kills off old schemas that aren't in use anymore.
>
> I am LMAO because Lisp (my server-side lang) does this to noobs, too: three
> (at least) ways to do everything. Well, if all things are equal dropping one
> schema and not kludging up mangled table names has a lot of appeal. Thx.
Schemas, search_path and views together can let you do some pretty
cool things in terms of integrating external postgresql based apps
with each other.
From | Date | Subject | |
---|---|---|---|
Next Message | Kenneth Tilton | 2009-04-08 02:32:39 | Re: nooby Q: temp tables good for web apps? |
Previous Message | Kenneth Tilton | 2009-04-08 01:12:54 | Re: nooby Q: temp tables good for web apps? |