Re: Store results by search term, not session ID

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

Comment on Re: Store results by search term, not session ID

Replies are listed 'Best First'.
Re: Re: Store results by search term, not session ID by perrin (Chancellor) on May 10, 2002 at 03:38 UTC
Hmmm... I had a reply node here and it seems to have been erased when I replied to ask below in the same thread. Very strange. Anyway, the gist of it was that you can use the table structure you suggested or serialize the whole result data structure into a blob column using Storable. Also, make if your search criteria are in a hash make sure you sort them before you use them as the result key. Hashes can return their keys in a different order, even when the keys are identical.	[reply]

Replies are listed 'Best First'.

Re: Re: Store results by search term, not session ID
by perrin (Chancellor) on May 10, 2002 at 03:38 UTC

ask

Anyway, the gist of it was that you can use the table structure you suggested or serialize the whole result data structure into a blob column using Storable.

Also, make if your search criteria are in a hash make sure you sort them before you use them as the result key. Hashes can return their keys in a different order, even when the keys are identical.

[reply]