| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: WIP: transformation hook modules and JSON support |
| Date: | 2009-04-01 02:38:15 |
| Message-ID: | 20090401023815.GB3377@alvh.no-ip.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Pavel Stehule escribió:
> Hello
>
> I am sending samples of transformation hook modules. One module is
> JSON support:.
>
> From these modules only JSON support has general usage - so only JSON
> should be integrated to core.
I'm only seeing trivial examples below, where you form the JSON objects
by plastering literals together. Does this work on a scenario where the
values come from a table?
The question is not at all theoretical -- right now our
archives.postgresql.org site uses a JSON file that's just a dump of a
table in a database. This file contains a list of lists, and a number
of properties for each (name, group it belongs to, description).
Obviously each one needs its label too.
Right now we generate this with a JSON Perl module.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Werner Echezuria | 2009-04-01 02:57:47 | Sort a column that does not exist |
| Previous Message | Alvaro Herrera | 2009-04-01 02:32:39 | Re: More message encoding woes |