[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-general
Subject:    Re: [GENERAL] Porting MySQL data types to PostgreSQL
From:       Tom Lane <tgl () sss ! pgh ! pa ! us>
Date:       2007-07-31 14:32:23
Message-ID: 19363.1185892343 () sss ! pgh ! pa ! us
[Download RAW message or body]

ptjm@interlog.com (Patrick TJ McPhee) writes:
> One problem with this idea is the treatment of implicit casts between
> numeric types in TypeCategory(). For implicit casts to work, the type's
> OID has to be listed in that function (i.e., it has to be a built-in type).

That's not the case.  There probably are some things that won't work
nicely if TypeCategory() doesn't recognize the type as numeric category,
but to claim that implicit casts won't work at all is wrong.

			regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
       choose an index scan if your joining column's datatypes do not
       match
[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic