On 9/4/14 5:54 PM, Craig Ringer wrote:
On 09/04/2014 02:48 AM, Robert Haas wrote:
To take another example, I've been complaining about the fact
that PostgreSQL 8.3+ requires far more typecasts in stored procedures
than any other database I'm aware of for years, probably since before
I joined EnterpriseDB.
+10
This still drives me nuts, and it's a serious problem for ORM users too.
The idea that we won't accept a 'text' typed input for an 'xml' or
'json' field is IMO absurdly and needlessly pedantic. I've not yet seen
an argument for what problems this solves.
In what context? Are we talking about parameters which have been cast
to text, or what? I don't remember ever having an issue with this,
though I remember the lack of implicit cast from text to json (or the
other way round) making a bug more obvious a couple of times.
.marko
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
