mirror/postgresql
2
0
Fork 0
mirror of https://git.postgresql.org/git/postgresql.git synced 2024-12-09 08:10:09 +08:00
Code Issues Packages Projects Releases Wiki Activity

Tweak TypeCategory to treat new BIT types as of STRING category, rather

Browse Source 
than not knowing what they are at all.  Perhaps they should have their own
type category?  Hard to say.  In the meantime, doing it this way allows
SELECT 'unknown' || 'unknown' to continue being resolved as textcat,
instead of spitting out an ambiguous-operator error.
This commit is contained in:
Tom Lane 2000-04-08 19:29:40 +00:00
parent b64e768595
commit bb7e5dc2c0
1 changed files with 14 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
src/backend/parser/parse_coerce.c
View File

@ -8,7 +8,7 @@
*
*
* IDENTIFICATION
* $Header: /cvsroot/pgsql/src/backend/parser/parse_coerce.c,v 2.40 2000/03/23 07:36:03 tgl Exp $
* $Header: /cvsroot/pgsql/src/backend/parser/parse_coerce.c,v 2.41 2000/04/08 19:29:40 tgl Exp $
*
*-------------------------------------------------------------------------
*/
@ -331,6 +331,19 @@ TypeCategory(Oid inType)
result = STRING_TYPE;
break;
/*
* Kluge added 4/8/00 by tgl: treat the new BIT types as strings,
* so that 'unknown' || 'unknown' continues to resolve as textcat
* rather than generating an ambiguous-operator error. Probably
* BIT types should have their own type category, or maybe they
* should be numeric? Need a better way of handling unknown types
* first.
*/
case (ZPBITOID):
case (VARBITOID):
result = STRING_TYPE;
break;
case (OIDOID):
case (REGPROCOID):
case (INT2OID):