Search Refinement

[John Hoge]

I'm working on a product search page that will allow the user to
refine their search results based on a few criteria.

The user will do a text search, which returns a set of products, and
then be presented with a series of checkboxes for product categories
and price buckets.

I have two options to do this:

Option 1 is to build a new query and go back to the database again for
the refined search.

Option 2 is to persist the original results in a DataSet and then use
the DefaultView.Filter property to restrict the data.

Option 1 will hit the DB more, and Option 2 will use more RAM. Coming
from a classic ASP background, I tend toward the first option, but the
second option seems to be a more "correct" .net technique. The number
of records returned in the original query is probably not going < 20.

Has anybody tried this and found any pros or cons either way?

 

[bruce barker]

is you are using a real database (say sqlserver) than i'd use the database.
it allows better filtering, and its queries are faster.

-- bruce (sqlwork.com)


| I'm working on a product search page that will allow the user to
| refine their search results based on a few criteria.
|
| The user will do a text search, which returns a set of products, and
| then be presented with a series of checkboxes for product categories
| and price buckets.
|
| I have two options to do this:
|
| Option 1 is to build a new query and go back to the database again for
| the refined search.
|
| Option 2 is to persist the original results in a DataSet and then use
| the DefaultView.Filter property to restrict the data.
|
| Option 1 will hit the DB more, and Option 2 will use more RAM. Coming
| from a classic ASP background, I tend toward the first option, but the
| second option seems to be a more "correct" .net technique. The number
| of records returned in the original query is probably not going < 20.
|
| Has anybody tried this and found any pros or cons either way?

 

[JerryK]

I would use the database.