| From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
|---|---|
| To: | "Ron Mayer" <rm_pg(at)cheapcomplexdevices(dot)com> |
| Cc: | "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:33:45 |
| Message-ID: | 87ird2lb4m.fsf@stark.xeocode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"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.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2007-03-15 16:49:10 | Re: My honours project - databases using dynamically attached entity-properties |
| Previous Message | Csaba Nagy | 2007-03-15 16:25:19 | Re: My honours project - databases using dynamically attached entity-properties |