Re: moving from MySQL to pgsql

From: Ondrej Ivanič <ondrej(dot)ivanic(at)gmail(dot)com>
To: Vineet Deodhar <vineet(dot)deodhar(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: moving from MySQL to pgsql
Date: 2012-10-10 23:56:27
Message-ID: CAM6mie+FkqobH22KWJNxCTMFpvgeO4M4Ju2p5jD_F_ffibVhyw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi,

On 10 October 2012 19:47, Vineet Deodhar <vineet(dot)deodhar(at)gmail(dot)com> wrote:
> 3) Can I simulate MySQL's TINYINT data-type (using maybe the custom data
> type or something else)

What do you exactly mean? Do you care about storage requirements or
constraints? The smallest numeric type in postgres is smallint: range
is +/- 32K and you need two bytes. You can use check constraint to
restrict the range (postgres doesn't have signed / unsigned types):

create table T (
tint_signed smallint check ( tint_signed >= -128 and tint_signed =< 127 ),
tint_unsigned smallint check ( tint_unsigned >= 0 and tint_unsigned =< 255 )
)

if you care about storage then "char" (yes, with quotes) might be the
right type for you.

--
Ondrej Ivanic
(ondrej(dot)ivanic(at)gmail(dot)com)
(http://www.linkedin.com/in/ondrejivanic)

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Darren Duncan 2012-10-11 00:17:15 Re: moving from MySQL to pgsql
Previous Message Tom Lane 2012-10-10 23:50:45 Re: Planner chooses multi-column index in 9.2 when maybe it should not