From: | Noah Misch <noah(at)leadboat(dot)com> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | Thom Brown <thom(at)linux(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: List of "binary-compatible" data types |
Date: | 2013-11-05 18:08:28 |
Message-ID: | 20131105180828.GA746099@tornado.leadboat.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Nov 05, 2013 at 10:00:15AM -0800, Josh Berkus wrote:
> Noah,
>
> >> Also, JSON <--> Text seems to be missing from the possible binary
> >> conversions. That's a TODO, I suppose.
> >
> > Only json --> text, not json <-- text. Note that you can add the cast
> > manually if you have an immediate need.
>
> Huh? Why would text --> JSON require a physical rewrite? We have to
> validate it, sure, but we don't need to rewrite it.
That's all true, but the system has no concept like "this cast validates the
data, never changing it". We would first need to add metadata supporting such
a concept. On the other hand, "create cast (json as text) without function;"
leans only on concepts the system already knows.
--
Noah Misch
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2013-11-05 18:13:10 | Better error message for window-function spec bizarreness |
Previous Message | Josh Berkus | 2013-11-05 18:00:15 | Re: List of "binary-compatible" data types |