On Tue, Aug 7, 2012 at 7:26 PM, Craig Ringer wrote:
> On 08/08/2012 03:45 AM, Merlin Moncure wrote:
>
>> Given that you can do that, if you had the ability to emit json from
>> an hstore the OP's problem would be trivially handled.
>
>
> That's where my thinking went at first too, but there's a wr
On 08/08/2012 03:45 AM, Merlin Moncure wrote:
Given that you can do that, if you had the ability to emit json from
an hstore the OP's problem would be trivially handled.
That's where my thinking went at first too, but there's a wrinkle with
that: json represents the number 1 and the string "1
On Tue, Aug 7, 2012 at 11:31 AM, Merlin Moncure wrote:
> On Tue, Aug 7, 2012 at 3:20 AM, Craig Ringer wrote:
>> (Reposted as the list manager appears to have eaten the first copy):
>>
>> Hey all
>>
>> It seems to be surprisingly hard to build JSON structures with PostgreSQL
>> 9.2's json features
On Tue, Aug 7, 2012 at 3:20 AM, Craig Ringer wrote:
> (Reposted as the list manager appears to have eaten the first copy):
>
> Hey all
>
> It seems to be surprisingly hard to build JSON structures with PostgreSQL
> 9.2's json features, because:
>
> - There's no aggregate, function or operator that
(Reposted as the list manager appears to have eaten the first copy):
Hey all
It seems to be surprisingly hard to build JSON structures with
PostgreSQL 9.2's json features, because:
- There's no aggregate, function or operator that merges two or more
objects; and
- there's no single-value "j
