mirror of
https://github.com/postgres/postgres.git
synced 2025-07-07 00:36:50 +03:00
Even after the great date/time consolidation, TypeCategory() was still
a few bricks shy of a load concerning knowing all the date/time types. This is real bad because it interferes with func_select_candidate()'s willingness to disambiguate functions --- func_select_candidate() will punt unless all the available choices have the same type category. I think this whole mechanism needs redesigned, but in the meantime this is a needed patch.
This commit is contained in:
@ -8,7 +8,7 @@
|
||||
*
|
||||
*
|
||||
* IDENTIFICATION
|
||||
* $Header: /cvsroot/pgsql/src/backend/parser/parse_coerce.c,v 2.30 2000/02/16 17:24:37 thomas Exp $
|
||||
* $Header: /cvsroot/pgsql/src/backend/parser/parse_coerce.c,v 2.31 2000/02/20 06:28:42 tgl Exp $
|
||||
*
|
||||
*-------------------------------------------------------------------------
|
||||
*/
|
||||
@ -298,12 +298,15 @@ TypeCategory(Oid inType)
|
||||
result = NUMERIC_TYPE;
|
||||
break;
|
||||
|
||||
case (DATEOID):
|
||||
case (TIMEOID):
|
||||
case (ABSTIMEOID):
|
||||
case (TIMESTAMPOID):
|
||||
result = DATETIME_TYPE;
|
||||
break;
|
||||
|
||||
case (RELTIMEOID):
|
||||
case (TINTERVALOID):
|
||||
case (INTERVALOID):
|
||||
result = TIMESPAN_TYPE;
|
||||
break;
|
||||
|
Reference in New Issue
Block a user