Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id B7FCB1648184 for ; Fri, 30 Mar 2012 11:32:23 -0300 (ADT) Received: from relay3-d.mail.gandi.net ([217.70.183.195]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1SDcsI-0001vx-Ea for pgsql-hackers@postgresql.org; Fri, 30 Mar 2012 14:32:23 +0000 X-Originating-IP: 217.70.178.130 Received: from mfilter1-d.gandi.net (mfilter1-d.gandi.net [217.70.178.130]) by relay3-d.mail.gandi.net (Postfix) with ESMTP id 1E683A8073; Fri, 30 Mar 2012 16:31:58 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mfilter1-d.gandi.net Received: from relay3-d.mail.gandi.net ([217.70.183.195]) by mfilter1-d.gandi.net (mfilter1-d.gandi.net [10.0.15.180]) (amavisd-new, port 10024) with ESMTP id Wzlpgbp263Q7; Fri, 30 Mar 2012 16:31:56 +0200 (CEST) X-Originating-IP: 98.27.54.176 Received: from [192.168.10.146] (cpe-098-027-054-176.nc.res.rr.com [98.27.54.176]) (Authenticated sender: adsend@dunslane.net) by relay3-d.mail.gandi.net (Postfix) with ESMTPSA id 2BCBCA8099; Fri, 30 Mar 2012 16:31:55 +0200 (CEST) Message-ID: <4F75C3DA.3000408@dunslane.net> Date: Fri, 30 Mar 2012 10:31:54 -0400 From: Andrew Dunstan User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.1) Gecko/20120216 Thunderbird/10.0.1 MIME-Version: 1.0 To: Merlin Moncure CC: Dobes Vandermeer , pgsql-hackers@postgresql.org Subject: Re: HTTP Frontend? (and a brief thought on materialized views) References: <4F7479FE.9050702@dunslane.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -1.9 (-) X-Archive-Number: 201203/1859 X-Sequence-Number: 205740 On 03/30/2012 09:57 AM, Merlin Moncure wrote: > What I'm saying is that jsonpath probably isn't the whole story: > another way of bulk moving json into native backend structures without > parsing would also be very helpful. For example, being able to cast a > json document into a record or a record array would be just amazing. It should be possible. After all, hstore's populate_record() does that. If we married that logic up with the json parser we should be half way there. cheers andrew