| From: | Ben Chobot <bench(at)silentmedia(dot)com> |
|---|---|
| To: | Neil Saunders <n(dot)j(dot)saunders(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Multiple counts on criteria - Approach to a problem |
| Date: | 2009-09-17 16:35:06 |
| Message-ID: | 4AB2653A.7080805@silentmedia.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Neil Saunders wrote:
> Hi all,
>
> I maintain an online property rental application. The main focus of
> the UI is the search engine, which I'd now like to improve by allowing
> filtering of the search results shown on some criteria, but provide a
> count of the number of properties that meet that criteria.
>
> For example, we're looking all properties, no criteria. I'd like to
> show something like:
>
> Bedrooms:
> 1 Bedroom (122)
> 2 Bedrooms (143)
> 3 Bedrooms (88)
>
> Facilities
> BBQ (232)
> Pool (122)
>
> ...and so on. My question is simple - What's the best way to implement
> this - Do I literally have to execute a count for the WHERE criteria
> with the filter criteria tagged on, or is there some clever trick that
> I'm not aware of? I'd rather not count in the application as I'd like
> to plan for the day we have up to 100k properties (
You could try using materialized views. Your churn is probably low
enough that it would make sense to update the views every time a
property is (de)listed.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | hubert depesz lubaczewski | 2009-09-17 16:40:08 | creation of foreign key without checking prior data? |
| Previous Message | Adam Rich | 2009-09-17 16:32:20 | Re: Multiple counts on criteria - Approach to a problem |