From: | Misa Simic <misa(dot)simic(at)gmail(dot)com> |
---|---|
To: | Atri Sharma <atri(dot)jiit(at)gmail(dot)com> |
Cc: | Merlin Moncure <mmoncure(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, PgHacker <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Graph datatype addition |
Date: | 2013-04-29 16:42:49 |
Message-ID: | CAH3i69nxF-g+ef17mEpAaECVjLRpuTLsYyO476BjyVarw0oB5w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi Atri,
What is an example of custom internal representation and its JSON
representation (though and JSON and HStore represent its value as text)?
I also think that the key question is: "what operations would you support
on this
data type?"
Or what kind of problems it will solve? (what can't be solved now - or can
now - but new type will allow the better way...)
Thanks,
Misa
2013/4/29 Atri Sharma <atri(dot)jiit(at)gmail(dot)com>
> >
> > I don't agree with this; JSON is not really designed to store graphs.
> > You will probably need a customized internal representation, just like
> > hstore, that expresses a graph like structure.
>
> Yes, we will have a custom internal representation. I was thinking of
> ways to export the graph into user parsable type, hence JSON.
>
>
>
> Regards,
>
> Atri
>
>
> --
> Regards,
>
> Atri
> l'apprenant
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>
From | Date | Subject | |
---|---|---|---|
Next Message | Misa Simic | 2013-04-29 16:47:53 | Re: Graph datatype addition |
Previous Message | Tom Lane | 2013-04-29 15:27:00 | Re: [PATCH] add --throttle option to pgbench |