pg.ddx.io pgsql-sql@postgresql.org mailing list archivehelp / color / mirror / Atom feed
From: BeemerBiker <jstateson@swri.edu>
To: pgsql-sql@postgresql.org
Subject: refining view using temp tables
Date: Tue, 31 Oct 2006 09:01:27 -0800 (PST)
Message-ID: <7097897.post@talk.nabble.com> (raw)
Using postgre with dotnet VS8. I came up with a scheme of having a web user
search thru the database and selecting into a temp table. Then a further
"refined" search would use the temp table as input and another temp table as
output. Then swap the source and destination so as to not use up resources.
Maybe this is not a good mechanism. I found right away I could not easily
check for table existence nor drop non-existent tables without getting a
server error (even with try {} catch {}).
I may have the same user bring up two or more pages during the same session.
Ditto for other users. I would not want to code up temporary names using
timestamps and usersnames if I could avoid it. It would be nice if the sql
engine would handle this for me. Can someone suggest how postgresql could
handle a google like "search within results".
--
View this message in context: http://www.nabble.com/refining-view-using-temp-tables-tf2546966.html#a7097897
Sent from the PostgreSQL - sql mailing list archive at Nabble.com.
view thread (2+ messages) latest in thread
Message-ID: <7097897.post@talk.nabble.com> Permalink: ../7097897.post@talk.nabble.com/ Also on: postgresql.org/message-id/7097897.post@talk.nabble.com ·
reply
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Reply to all the recipients using the --to and --cc options: reply via email To: pgsql-sql@postgresql.org Cc: jstateson@swri.edu Subject: Re: refining view using temp tables In-Reply-To: <7097897.post@talk.nabble.com> * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox