On Wed, Nov 21, 2012 at 3:16 PM, Andrew Dunstan <andrew@dunslane.net> wrote:
> Non-builtin types are now searched for a cast to json, and if it exists it
> is used instead of the type's text representation. I didn't add a special
> type to look for a cast to, as was discussed before, as it seemed a bit
> funky and unnecessary. It can easily be added, but I'm still not convinced
> it's a good idea. Note that this is only done for types that aren't builtin
> - we know how to turn all of those into json without needing to look for a
> cast.
The place where I fear this will cause problems is with non-core
text-like datatypes, such as citext. For example, I wonder if
creating a cast from citext to json - which seems like a sensible
thing to want to do for other reasons - changes the semantics of this
function when applied to citext objects.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
