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 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
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
From | Date | Subject | |
---|---|---|---|
Next Message | andrea gelmini | 2002-01-11 20:03:41 | Re: ehm... |
Previous Message | Grant Johnson | 2002-01-11 19:02:44 | Re: createlang |