Re: "anyelement2" pseudotype
От | Tom Lane |
---|---|
Тема | Re: "anyelement2" pseudotype |
Дата | |
Msg-id | 27787.1171478048@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: "anyelement2" pseudotype (Tom Dunstan <pgsql@tomd.cc>) |
Ответы |
Re: "anyelement2" pseudotype
|
Список | pgsql-hackers |
Tom Dunstan <pgsql@tomd.cc> writes: > Regarding the type system understanding ANYENUM, most of the type system > treats ANYENUM identically to ANYELEMENT, the only parts that really > need to understand it are the bits that try to tie down concrete types. The reason I'm feeling annoyed with ANYfoo stuff today is that yesterday I had to put a special hack for ANYARRAY into the ri_triggers code, which you'd think would have no concern with it. But perhaps this is just an indication that we need to refactor the code in parse_coerce.c. (The problem in ri_triggers is that it uses find_coercion_pathway() which does not concern itself with ANYfoo types.) Anyway, objection withdrawn --- I just thought it seemed a good idea to question whether we were adding a frammish we didn't really need. regards, tom lane
В списке pgsql-hackers по дате отправления: