| From: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>, Jan Urbański <wulczer(at)wulczer(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, "David E(dot) Wheeler" <david(at)kineticode(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Joey Adams <joeyadams3(dot)14159(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Claes Jakobsson <claes(at)gluefinance(dot)com>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org>, Jan Wieck <janwieck(at)yahoo(dot)com> |
| Subject: | Re: JSON for PG 9.2 |
| Date: | 2011-12-19 10:49:03 |
| Message-ID: | 8739cgx2e8.fsf@hi-media-techno.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Merlin Moncure <mmoncure(at)gmail(dot)com> writes:
> Getting back on point, I'm curious about your statement: "without
> writing a single line of C". I took a look at the pl/scheme docs and
> was pretty impressed -- what exactly would be involved to get a
> guile-based ECMAscript working over the pl/scheme implementation? How
> would that interact exactly with the stated topic -- JSON support? Do
> you even need a json type if you have strong library based parsing and
> composition features?
My understanding is that JSON is a subset of ECMAscript, so if you get
the latter you already have the former. Now, someone would have to
check if plscheme still build with guile-2.0, and given that, how
exactly you get pl/ecmascript (or pl/js) out of that.
I won't be in a position to spend time on that this year…
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2011-12-19 11:10:11 | Re: Page Checksums |
| Previous Message | Marti Raudsepp | 2011-12-19 10:16:19 | [PATCH] Enable min/max optimization for bool_and/bool_or/every |