| From: | Thomas Lockhart <thomas(at)fourpalms(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Zeugswetter Andreas SB SD <ZeugswetterA(at)spardat(dot)at>, Thomas Lockhart <lockhart(at)fourpalms(dot)org>, Barry Lind <barry(at)xythos(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Implicit coercions need to be reined in |
| Date: | 2002-04-17 14:42:52 |
| Message-ID: | 3CBD89EC.2CC9000F@fourpalms.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
...
> What I'm really looking for is a way that we can allow (some?) implicit
> text coercions while getting rid of the sort of misbehavior exemplified
> by that bug report I keep referring to. Has anyone got any ideas about
> how to do that? It's one thing to say that "apples || oranges" should
> be interpreted as "apples::text || oranges::text", but it is quite
> another to say that "apples <= oranges" should be handled that way.
Hmm. istm that we might need some information to travel with the
operators, not just the coersion functions themselves. We have a fairly
type-rich system, but need to preserve the ability to add types and a
*partial* set of functions and operators and get reasonable behaviors.
- Thomas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-04-17 14:52:27 | Re: Implicit coercions need to be reined in |
| Previous Message | Larry Rosenman | 2002-04-17 14:41:29 | Re: [SQL] 16 parameter limit |