On Fri, Sep 13, 2013 at 7:52 PM, Chris Travers wrote:
> On Fri, Sep 13, 2013 at 8:51 AM, Merlin Moncure wrote:
>> What's your client side stack?
>>
>> merlin
>
>
> Right now we are using something a little lighter weight in terms db
> discovery but it doesn't handle this situation very well. I a
On Fri, Sep 13, 2013 at 8:51 AM, Merlin Moncure wrote:
>
>
> What's your client side stack?
>
> merlin
>
Right now we are using something a little lighter weight in terms db
discovery but it doesn't handle this situation very well. I am the author
of the PGObject space on CPAN and currently we
On Fri, Sep 13, 2013 at 10:08 AM, Chris Travers wrote:
> On Fri, Sep 13, 2013 at 7:58 AM, Merlin Moncure wrote:
>> Yup. As things stand currently, it's better *not* to make
>> serialization-driving composite types which when learning the json
>> stuff I did heavily; it was a habit I learned (and
On Fri, Sep 13, 2013 at 7:58 AM, Merlin Moncure wrote:
> Yup. As things stand currently, it's better *not* to make
> serialization-driving composite types which when learning the json
> stuff I did heavily; it was a habit I learned (and had to unlearn)
> from libpqtypes which solves a lot of t
On Fri, Sep 13, 2013 at 9:30 AM, Chris Travers wrote:
>
>
>
> On Fri, Sep 13, 2013 at 6:37 AM, Merlin Moncure wrote:
>>
>>
>>
>> It would certainly be better if we could straight up deserialize json
>> into a nested structure. For now, my advise is to try and structure
>> your json and the recei
On Fri, Sep 13, 2013 at 6:37 AM, Merlin Moncure wrote:
>
>
> It would certainly be better if we could straight up deserialize json
> into a nested structure. For now, my advise is to try and structure
> your json and the receiving types/tables to not be nested. Using your
> example, I was able
On Thu, Sep 12, 2013 at 7:25 PM, Chris Travers wrote:
>
>
>
> On Thu, Sep 12, 2013 at 8:47 AM, Merlin Moncure wrote:
>>
>>
>>
>> Can we see a hypothetical example? json best practices for me are to
>> use standard tables and than serialize/deserialize json as it goes
>> through the door and not
On Thu, Sep 12, 2013 at 8:47 AM, Merlin Moncure wrote:
>
>
> Can we see a hypothetical example? json best practices for me are to
> use standard tables and than serialize/deserialize json as it goes
> through the door and not use nested composite types in your actual
> table definitions. I thin
On Wed, Sep 11, 2013 at 11:55 PM, Chris Travers wrote:
> Hi everyone;
>
> I have been starting to experiment with the JSON accessors in 9.3. I
> immediately found that my preferred use, populating nested composite types,
> is not supported. Also of course one cannot manipulate JSON nodes, which
