Thanks Oren! That's exactly what I need. The indexed property bundle lets me get this base price calculation out of the way of our already-complex search requirements.
There are simple community lists all over the site, but those aren't a concern. We have one "Find a home" page where the criteria can really get out of hand. An example might be "Show me homes in Northwest Houston under $310,000 with at least 4 bedrooms and a 2 car garage, with a golf course and pool nearby"
The city, part of town, and nearby amenities are stored in the community doc and the rest is in the floor plan docs.
The displayed results would be something like this:
Bridgeland, from the $240s, 2500-5000 sq ft.
- The Beezer, from the $260s, 2600 sq ft, 4 bedrooms, 2.5 baths, 2 car garage
- The Barker, from the $300s, 3300 sq ft, 4 bedrooms, 3 baths, 2 car garage
The Cove, from the $190s, 2400-3400 sq ft
- The Bellville, from the $200s, 2600 sq ft, 4 bedrooms, 2 baths, 2 car garage
I expect the actual results from Raven will be some flat composite of community & floor plan data sorted by community. We'll do the grouping as we loop through the result.
We're not sure if this one complex search page is something we should even be doing with Raven. We're also considering doing the more complex filtering in memory, or replicating to SQL server and querying there. We haven't tried any of it yet, but if you've got ideas...
- J