Subject Re: [firebird-support] firebird 2.1
Author Tiberiu Horvath

I get it. One feature that I used is not a feature but a bug. Now I am very happy that the bug was resolved !

I will create a temporary field, with the new scale, then update and then drop.

Thank you,


----- Original Message ----
From: Helen Borrie <helebor@...>
Sent: Friday, April 25, 2008 1:09:47 PM
Subject: Re: [firebird-support] firebird 2.1

At 05:09 PM 25/04/2008, you wrote:
>Now the link
>http://tracker. firebirdsql. org/browse/ CORE-1162
>works for me.
>I do not understand what am I supposed to do.

Just don't try to raise the scale of the column - it is illegal now. ;-) Fb 2.0.x and also Fb 1.5.x allowed it, and it would (potentially) permit an overflow of the implemented precision limit and corrupt the database. That was a bug.

>this is the exact description of my problem :
>SQL> create table tab ( a numeric(4,2) );
>SQL> insert into tab values (99.99);
>SQL> alter table tab alter a type numeric(4,3) ;
>Statement failed, SQLCODE = -607
>unsuccessful metadata update
>-New scale specified for column A must be at most 2.

Your "history" ("I could do this in v.2.0.x") shows how the bug exhibited itself and your "problem" demonstrates that the bug is fixed.


Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now.;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ