| From: | Dimitri Fontaine <dfontaine(at)hi-media(dot)com> |
|---|---|
| To: | Hitoshi Harada <umi(dot)tanuki(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com>, Joseph Adams <joeyadams3(dot)14159(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: patch: Add JSON datatype to PostgreSQL (GSoC, WIP) |
| Date: | 2010-08-26 09:53:36 |
| Message-ID: | 87iq2x66ov.fsf@hi-media-techno.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hitoshi Harada <umi(dot)tanuki(at)gmail(dot)com> writes:
> It depends on use cases, but in my mind plain text will do for us. If
> we have JavaScript engine in PostgreSQL like pl/v8 and it handles
> on-disk format as-is, then we should choose the kind of format, but in
> either text or binary format way it is hopeless to have such
> compelling environment in the short future.
Well, for javascript support, there's another nice thing happening:
- plscheme is built on GNU Guile
- next version of GNU Guile supports javascript too
http://plscheme.projects.postgresql.org/
http://wingolog.org/archives/2009/02/22/ecmascript-for-guile
So my current guess at which javascript engine we'd get first would be
plscheme. Now I don't know what implication that would have on the
binary storage format of javascript or json documents.
Regards,
--
dim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dimitri Fontaine | 2010-08-26 09:54:49 | Re: EXPLAIN doesn't show the actual function expression for FunctionScan |
| Previous Message | Andrew Dunstan | 2010-08-26 09:24:51 | Re: WIP: extensible enums |