I was just testing my product running on a 7.3 snapshot from a few days
ago. And I ran into the following change in behavior that I consider a
bug. You can no long insert large values into a bigint column without a
cast. Small values (in the int range work fine though).
On 7.3 I get:
files
Dang it...meant to mention that the other day when I was working on
those python patches. I had to place tick marks (single quote) around
the number and it was converted correctly.
gcope=# insert into a values ( 99 ) ;
ERROR: column "a" is of type 'bigint' but expression is of type 'dou
Barry Lind <[EMAIL PROTECTED]> writes:
> You can no long insert large values into a bigint column without a
> cast.
This seems to be fallout from the move to tighten up implicit coercions
(cf http://archives.postgresql.org/pgsql-hackers/2002-04/msg00528.php
as well as lots of earlier discussions
Then shouldn't this appear on the "Open 7.3 issues" list that has been
circulating around? This seems like an open issue to me, that needs to
be addressed before 7.3 ships.
--Barry
Tom Lane wrote:
>Barry Lind <[EMAIL PROTECTED]> writes:
>
>
>>You can no long insert large values into a bigi
Barry Lind <[EMAIL PROTECTED]> writes:
> Then shouldn't this appear on the "Open 7.3 issues" list that has been
> circulating around?
It does.
regards, tom lane
---(end of broadcast)---
TIP 3: if posting/reading through Us
It is already there, I think:
fix implicit type coercions that are worse
---
Barry Lind wrote:
> Then shouldn't this appear on the "Open 7.3 issues" list that has been
> circulating around? This seems like an ope
