| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
| Cc: | Jeff Davis <pgsql(at)j-davis(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Feature Request: JSON input for hstore |
| Date: | 2009-09-14 23:45:46 |
| Message-ID: | 603c8f070909141645u81195cbq89ad1749656ff484@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Sep 14, 2009 at 7:42 PM, David E. Wheeler <david(at)kineticode(dot)com> wrote:
> On Sep 14, 2009, at 4:32 PM, Robert Haas wrote:
>
>>> What's wrong with just using a variant of the type input function? With
>>> a parameterized insert, it doesn't seem like it's really placing much of
>>> a burden on the application.
>>
>> Agreed, I was thinking the same thing.
>
> And the type output function, too. Not sure how you'd configure that,
> though.
Well I don't think you really need any them to BE the type
input/output functions. You just need
hstore_to_json(hstore) returns text
json_to_hstore(text) returns json
Insert into your query where appropriate.
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | ljb | 2009-09-15 00:28:02 | Patch for 1-byte buffer overflow in libpq PQencryptPassword |
| Previous Message | David E. Wheeler | 2009-09-14 23:42:14 | Re: Feature Request: JSON input for hstore |