From: | tomas(at)tuxteam(dot)de |
---|---|
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 15:52:06 |
Message-ID: | 20070315155206.GC26146@www.trapp.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, Mar 15, 2007 at 08:31:24AM -0700, Ron Mayer wrote:
> 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.
Do give hstore a try. It indexes over name/value mappings (the same
authors have intarray, indexing over arrays). If it doesn't solve your
problem it'll be at least a very good starting point for what you
mention above (basically it's a lossy GiST index based on a hash bitmap.
I was at least quite impressed).
Regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFF+WumBcgs9XrR2kYRAukhAJ9mPk89FfLX4E3dIBGlhfVTwqup0QCdE8Tx
nh05Y1WpyX36uKI+9qspO60=
=C/5K
-----END PGP SIGNATURE-----
From | Date | Subject | |
---|---|---|---|
Next Message | A.M. | 2007-03-15 16:01:59 | Re: My honours project - databases using dynamically attached entity-properties |
Previous Message | Ron Mayer | 2007-03-15 15:31:24 | Re: My honours project - databases using dynamically attached entity-properties |