| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: data to json enhancements |
| Date: | 2012-09-27 14:37:23 |
| Message-ID: | CA+TgmoaKFX8YxdG2wJe7oiNBHpo4TojSUZC-mCkj5=yKyuHGow@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Sep 27, 2012 at 10:09 AM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> So how about this suggestion: we'll look for a visible function named
> "as_json" or some such which has one parameter of the given type and returns
> json, and if it's present use it instead of the standard text
> representation. As an optimization we'll skip that lookup for builtin types,
> since there won't be one. Of course, we'll have one for hstore.
I think that general approach has some promise, although there are
some security issues to worry about.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Misa Simic | 2012-09-27 14:42:30 | Re: data to json enhancements |
| Previous Message | Tom Lane | 2012-09-27 14:36:47 | Re: data to json enhancements |