If drive space is not an issue on the database server, is there harm in making a temp table in the following format?

- search criteria
- result column 1
- result column 2
. . .

The reason I ask being that my search results will always have the same column names and ordering.

And, as for storing the criteria in the table, I imagine I can consolidate it into some sort of string like:
type=name;criteria1=this;criteria2=that;criteria3=blah

then index that field, consolidate a query into that format, and see if I get a match in the database? If not, cache some more data?

Thanks for the help thus far :)
MrCromeDome


In reply to Re: Store results by search term, not session ID by MrCromeDome
in thread Database searches with persistent results via CGI by MrCromeDome

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":