Re: Migration - not null default '0' -> not null default 0 - confused - Mailing list pgsql-general

From Adrian Klaver
Subject Re: Migration - not null default '0' -> not null default 0 - confused
Date
Msg-id 201003301803.41035.adrian.klaver@gmail.com
Whole thread Raw
In response to Re: Migration - not null default '0' -> not null default 0 - confused  (Jeff Davis <pgsql@j-davis.com>)
List pgsql-general
On Tuesday 30 March 2010 4:59:30 pm Jeff Davis wrote:
> On Tue, 2010-03-30 at 16:32 -0700, Adrian Klaver wrote:
> > 8.3 tightened up type casting. You cannot INSERT a '0' without casting it
> > to an integer i.e '0'::integer.
>
> I don't think that's accurate:
>
>   postgres=# select version();
>
> version
>
> ---------------------------------------------------------------------------
>----------------------------------------- --
>  PostgreSQL 9.0devel on x86_64-unknown-linux-gnu, compiled by GCC
> gcc-4.3.real (Ubuntu 4.3.2-1ubuntu12) 4.3.2, 64-bit
> (1 row)
>
>   postgres=# create table ints(i int);
>   CREATE TABLE
>   postgres=# insert into ints values('0');
>   INSERT 0 1
>
>
> Regards,
>     Jeff Davis

My mistake. I could of swore I had problems with this when I first tried 8.3.
What happens when you rely on memory.

--
Adrian Klaver
adrian.klaver@gmail.com

pgsql-general by date:

Previous
From: Steve Atkins
Date:
Subject: Re: Migration - not null default '0' -> not null default 0 - confused
Next
From: "Marc G. Fournier"
Date:
Subject: plPgSQL + CDIR/INET types ...