Dmitry Macsema <[EMAIL PROTECTED]> 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
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
