refining view using temp tables

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.