Re: Implicit coercions need to be reined in
От | Thomas Lockhart |
---|---|
Тема | Re: Implicit coercions need to be reined in |
Дата | |
Msg-id | 3CBD89EC.2CC9000F@fourpalms.org обсуждение исходный текст |
Ответ на | Re: Implicit coercions need to be reined in ("Zeugswetter Andreas SB SD" <ZeugswetterA@spardat.at>) |
Ответы |
Re: Implicit coercions need to be reined in
|
Список | 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
В списке pgsql-hackers по дате отправления: