Re: My honours project - databases using dynamically attached entity-properties

From: tomas(at)tuxteam(dot)de
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Gregory Stark <stark(at)enterprisedb(dot)com>, 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-17 12:39:54
Message-ID: 20070317123954.GB428@www.trapp.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, Mar 16, 2007 at 09:56:23AM -0400, Andrew Dunstan wrote:
> tomas(at)tuxteam(dot)de wrote:
> >
> >>Does hstore nest? [...]
> >
> >If what you mean is to have "mappings of mappings" then no.
> > [...] think "hash" for perl folks [...]

> As a perl folk I think of hashes as nestable :-)

Heh. Point taken :-)

> Anyway, this means that you can't use hstore to cover the same field as
> YAML or JSON. That doesn't mean it's not useful - far from it.

I think that hstore might be extensible in this direction. After all,
the keys and (key, value) combinations just get hashed into a bitmap.
There is no reason why one shouldn't be able to hash more complex data
structures (unless, of course, the bit map gets so densely poked with
ones that it stops being useful). The difficult part might be to reach a
consensus on what a "complex data structure" might look like.

The purists among the relational folks are sharpening their knives
already, I can hear that ;-)

Regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFF++GaBcgs9XrR2kYRAs/hAJ9vfRy36T23vJ6eIYj6efrQVk9roQCeMkqQ
kWqzNbgbkMOXKIDQuzwDeFY=
=fCiG
-----END PGP SIGNATURE-----

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2007-03-17 13:38:56 Bison 2.1 on win32
Previous Message Grzegorz Jaskiewicz 2007-03-17 10:11:03 Re: [PATCHES] Bitmapscan changes