Re: Porting MySQL data types to PostgreSQL - Mailing list pgsql-general

From ptjm@interlog.com (Patrick TJ McPhee)
Subject Re: Porting MySQL data types to PostgreSQL
Date
Msg-id 13aqo5d7n7d5801@corp.supernews.com
Whole thread Raw
In response to Porting MySQL data types to PostgreSQL  ("Gautam Sampathkumar" <gsampathkumar@gmail.com>)
Responses Re: Porting MySQL data types to PostgreSQL
List pgsql-general
In article <B396176E-A0FC-43CF-8C67-38CB1AF6A520@decibel.org>,
Jim Nasby <decibel@decibel.org> wrote:
% On Jul 26, 2007, at 11:06 AM, Jeff Davis wrote:
% > If you really do need an unsigned type, this is a good use of
% > postgresql's extensible type system. You can just create an unsigned
% > type for yourself.
%
% If you do that please start a project on pgfoundry so others can
% contribute and benefit. In fact, if you do start one let me know and
% I'll try and help out.

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).
--

Patrick TJ McPhee
North York  Canada
ptjm@interlog.com

pgsql-general by date:

Previous
From: Viatcheslav Kalinin
Date:
Subject: Polymorphic functions' weird behavior
Next
From: pc
Date:
Subject: Re: query to match '\N'