| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
| Cc: | John R Pierce <pierce(at)hogranch(dot)com>, Merlin Göttlinger <megoettlinger(at)gmail(dot)com>, Mike Christensen <mike(at)kitchenpc(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL specific datatypes very confusing for beginners who use wrappers around JDBC |
| Date: | 2014-01-29 06:01:48 |
| Message-ID: | 17514.1390975308@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Craig Ringer <craig(at)2ndquadrant(dot)com> writes:
> I just want us to allow, by default, implicit casts FROM text (not TO
> text) using the input function for all PostgreSQL's validated
> non-standard types (and XML due to limited deployment of SQL/XML support
> in client drivers).
Sorry, that is *just* as dangerous as implicit casts to text were.
It would bite a different set of queries, but not any less painfully.
I have about zero sympathy for ORMs that aren't willing to address
this issue properly. Yeah, it might be less than trivial, but that
doesn't mean that the right answer is to create semantic hazards
on the server side.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Johnston | 2014-01-29 06:36:01 | Re: PostgreSQL specific datatypes very confusing for beginners who use wrappers around JDBC |
| Previous Message | Tom Lane | 2014-01-29 05:22:39 | Re: PostgreSQL specific datatypes very confusing for beginners who use wrappers around JDBC |