Skip site navigation (1) Skip section navigation (2)

Re: Bad integer

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Dmitry Macsema <dmacsema(at)iname(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Bad integer
Date: 2002-01-11 19:16:19
Message-ID: 593.1010776579@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Dmitry Macsema <dmacsema(at)iname(dot)com> writes:
>   I'm getting "Bad integer 4020239173" error. From what I found on the
>   Web it seems to be a Postgres bug, not specific to any programming
>   language.

First I've heard of it.  You're going to have to provide a lot more
information if you want us to believe it's a Postgres problem.

The only occurrence of the string "bad integer" in current postgres
sources is

src/interfaces/jdbc/org/postgresql/errors.properties: postgresql.res.badint:Bad Integer {0}

which appears to be an exception thrown only by toInt().  Complaining
because someone tried to coerce an oversize value to integer is not
obviously a bug...

			regards, tom lane

In response to

  • Bad integer at 2002-01-11 00:54:40 from Dmitry Macsema

pgsql-bugs by date

Next:From: andrea gelminiDate: 2002-01-11 20:03:41
Subject: Re: ehm...
Previous:From: Grant JohnsonDate: 2002-01-11 19:02:44
Subject: Re: createlang

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group