Re: additional json functionality

On Nov 16, 2013, at 2:04 PM, Hannu Krosing <hannu(at)2ndquadrant(dot)com> wrote:

>> It’s still input and output as JSON, though.
> Yes, because JavaScript Object Notation *is* a serialization format
> (aka Notation) for converting JavaScript Objects to text format
> and back :)
>> I still like JSONB best.
> To me it feels redundant, like binarytextbinary
>
> the binary representation of JSON is JavaScript(-like) Object, not
> "binary json"
>
> So my vote would be either jsobj or jsdoc (as "document databases") tend
> to call the structured types "documents"

You know that both types support scalar values right? 'a'::JSON works now, and 'a'::hstore works with the WIP patch. For that reason I would not think that "doc" or "obj" would be good choices.

I like JSONB because:

1. The "B" means "binary"
2. The "B" means "second"
3. It's short
4. See also BYTEA.

Best,

David