Re: [GENERAL] Porting MySQL data types to PostgreSQL

2007-08-04 Thread Tom Lane
Decibel! <[EMAIL PROTECTED]> writes: > Be that as it may, I suspect that if someone puts forward a working set > of uint2/4/8 it'd be considered for inclusion. The datatypes themselves are utterly trivial. The hard part, if you want them to be part of the numeric hierarchy, is figuring out what t

Re: [GENERAL] Porting MySQL data types to PostgreSQL

2007-08-04 Thread Decibel!
On Wed, Aug 01, 2007 at 05:19:33AM -, Patrick TJ McPhee wrote: > In article <[EMAIL PROTECTED]>, > Tom Lane <[EMAIL PROTECTED]> wrote: > % [EMAIL PROTECTED] (Patrick TJ McPhee) writes: > % > One problem with this idea is the treatment of implicit casts between > % > numeric types in TypeCategor

Re: [GENERAL] Porting MySQL data types to PostgreSQL

2007-08-04 Thread Patrick TJ McPhee
In article <[EMAIL PROTECTED]>, Tom Lane <[EMAIL PROTECTED]> wrote: % [EMAIL PROTECTED] (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

Re: [GENERAL] Porting MySQL data types to PostgreSQL

2007-07-31 Thread Tom Lane
[EMAIL PROTECTED] (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

Re: [GENERAL] Porting MySQL data types to PostgreSQL

2007-07-31 Thread Patrick TJ McPhee
In article <[EMAIL PROTECTED]>, Jim Nasby <[EMAIL PROTECTED]> 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 tha

Re: [GENERAL] Porting MySQL data types to PostgreSQL

2007-07-28 Thread Jim Nasby
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 fac

Re: [GENERAL] Porting MySQL data types to PostgreSQL

2007-07-26 Thread Jeff Davis
On Tue, 2007-07-24 at 10:47 -0700, Gautam Sampathkumar wrote: > Hi, >I am in the process of porting a MySQL database to PostgreSQL. > I was wondering why PostgreSQL does not support unsigned data types? > > Does this mean I'd have to essentially double the space occupied by > most database

Re: [GENERAL] Porting MySQL data types to PostgreSQL

2007-07-25 Thread Michael Glaesemann
[Please reply to the list so that others may benefit from and participate in the discussion, and please don't top post as it makes the discussion more difficult to follow.] On Jul 25, 2007, at 20:55 , Gautam Sampathkumar wrote: Thank you for your answer. Do you know why a choice w

Re: [GENERAL] Porting MySQL data types to PostgreSQL

2007-07-25 Thread Michael Glaesemann
On Jul 24, 2007, at 12:47 , Gautam Sampathkumar wrote: Does this mean I'd have to essentially double the space occupied by most database columns e.g convert mysql integer to postgresql bigint? Only if your unsigned 4-byte integers actually exceed 2,147,483,647. I suppose you could also us