On 9/25/12 9:18 AM, Andrew Dunstan wrote:
> No, the difficulty (or at least the first difficulty) is in having the
> code recognize that it has an hstore at all. The code picks apart the
> record field by field at run time and takes various actions depending on
> the field's type. For any type it doesn't recognize it just outputs the
> value as a string, and so that's what it does with hstore. Mostly this
> is the right thing but in the hstore case it's rather sad.
But if you have a cast defined from hstore to json, then it is
unambiguous, because the pg_cast entry binds the types together by OID.
