Re: My honours project - databases using dynamically attached entity-properties - Mailing list pgsql-hackers

From Ron Mayer
Subject Re: My honours project - databases using dynamically attached entity-properties
Date
Msg-id 45F966CC.2050700@cheapcomplexdevices.com
Whole thread Raw
In response to Re: My honours project - databases using dynamically attached entity-properties  (Josh Berkus <josh@agliodbs.com>)
Responses Re: My honours project - databases using dynamically attached entity-properties  (tomas@tuxteam.de)
Re: My honours project - databases using dynamically attached entity-properties  ("A.M." <agentm@themactionfaction.com>)
Re: My honours project - databases using dynamically attached entity-properties  (Gregory Stark <stark@enterprisedb.com>)
List pgsql-hackers
Josh Berkus wrote:
>> And then what? dynamically construct all your SQL queries?
>> Sure, sounds like a simple solution to me...
> 
> Not to mention DB security issues.  How do you secure your database when 
> your web client has DDL access?
> 
> So, Edward, the really *interesting* idea would be to come up with a 
> secure, normalized way to do UDFs *without* EAV tables.  People would be 
> very impressed.
> 

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.


pgsql-hackers by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: [PATCHES] Bitmapscan changes
Next
From: tomas@tuxteam.de
Date:
Subject: Re: My honours project - databases using dynamically attached entity-properties