On Wed, Dec 21, 2011 at 8:32 PM, Johann 'Myrkraverk' Oskarsson
<johann@2ndquadrant.com> wrote:
> I mean to create a typed hstore, called tstore for now. I'm open to
> name suggestions. It'll only support a subset of core Postgres types
> to begin with. Keys are always text, it's the value that's typed.
Unfortunately, I'm not sure it'll be of much interest unless it heads
all the way to having nested data.
JSON is the "thing of the day" that it would be desirable for this to
be potent enough to represent, and JSON has the following types:
1. Number (in practice, FLOAT)
2. String (UTF-8)
3. Boolean (t/f)
4. Array (not necessarily of uniform type
5. Object (string key, JSON value pairs, unordered)
6. NULL
#4 and #5 are obviously entirely more "hairy."
But it seems pretty likely that people would be keen on additional
implementations until they get those.
--
When confronted by a difficult problem, solve it by reducing it to the
question, "How would the Lone Ranger handle this?"