From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Gregory Stark <stark(at)enterprisedb(dot)com> |
Cc: | Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: My honours project - databases using dynamically attached entity-properties |
Date: | 2007-03-15 16:49:10 |
Message-ID: | 45F97906.8000804@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Gregory Stark wrote:
> "Ron Mayer" <rm_pg(at)cheapcomplexdevices(dot)com> writes:
>
>
>> I have a system with many essentially user-defined fields, and was
>> thinking of creating something similar to an Array type and writing
>> some GIST indexes for it.
>>
>> My current workaround is to store them as a YAML document and use
>> tsearch to index it (with application logic to further refine the
>> results) - but a EAV datatype that could be put in tables and
>> effectively indexed would be of quite a bit of interest here.
>> And yes, a better say to do UDFs would be even cooler.
>>
>
> I think that's what hstore does. Honestly I'm not entirely certain though.
>
>
Does hstore nest? My impression is that it doesn't. Which might well not
matter, of course.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-03-15 18:09:57 | Proposal: minor SPI interface change |
Previous Message | Gregory Stark | 2007-03-15 16:33:45 | Re: My honours project - databases using dynamically attached entity-properties |