Ah hah! This appears to be what I'm interested in doing.
I'll have to read up on object_types.
+--------------------------------------------------------+
| Matthew Runo
| Zappos Development
| [EMAIL PROTECTED]
| 702-943-7833
+--------------------------------------------------------+
On Apr 19, 2007, at 10:04 AM, Cody Caughlan wrote:
Why not just store an additional "object_type" field which
differentiates between the actual type of data you are looking for?
So if you're looking for some shoes:
(size:8 AND color:'blue') AND object_type:'shoe'
Or if you're searching on brands
(genre:'skater' AND brand_desc:'skater boy') AND object_type:'brand'
I apologize if I misunderstood your question.
/cody
On 4/19/07, Matthew Runo <[EMAIL PROTECTED]> wrote:
Hey there-
I was wondering if the following was possible, and, if so, how to set
it up...
I want to index two different types of data, and have them searchable
from the same interface.
For example, a group of products, with size, color, price, etc info.
And a group of brands, with brand, genre, brand description, etc info
So, the info does overlap some. But a lot of the fields for each
"type" don't matter to the other. Is there a way to set up two
different schema so that both types may be indexed with relative
ease?
+--------------------------------------------------------+
| Matthew Runo
| Zappos Development
| [EMAIL PROTECTED]
| 702-943-7833
+--------------------------------------------------------+
