gt; not a long.
>>>>>>>
>>>>>>> BatchUpdateException
>>>>>>> executeBatch
>>>>>>>
>>>>>>> I'm thinking the only option here is to report INT_MAX as opposed to
>>>>>>> failing.
>>>>>>>
>>>>>>> Thoughts ?
>>>>>>>
>>>>>>> Dave
>>>>>>>
>>>>>>>
>>>>>>> Dave Cramer
>>>>>>>
>>>>>>> dave.cramer(at)credativ(dot)ca
>>>>>>> http://www.credativ.ca
>>>>>>>
>>>>>>>
>>>>>>> On Fri, Dec 21, 2012 at 3:17 PM, Tom Lane wrote:
>>>>>>>
>>>>>>>> Dave Cramer writes:
>>>>>>>> > So an unsigned long won't fit inside a java long either, but
>>>>>>>> hopefully it
>>>>>>>> > will never be necessary. That would be a huge number of changes.
>>>>>>>>
>>>>>>>> I think we'll all be safely dead by the time anybody manages to
>>>>>>>> process
>>>>>>>> 2^63 rows in one PG command ;-). If you can widen the value from
>>>>>>>> int to
>>>>>>>> long on the Java side, that should be sufficient.
>>>>>>>>
>>>>>>>> regards, tom lane
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>>
>
--
Best regards,
Vitalii Tymchyshyn
The following bug has been logged online:
Bug reference: 5411
Logged by: Vitalii Tymchyshyn
Email address: tiv...@gmail.com
PostgreSQL version: 8.4.3
Operating system: OpenSuse 11.2: Linux tivv 2.6.31.12-0.1-default #1 SMP
2010-01-27 08:20:11 +0100 x86_64 x86_64 x86_64 GNU
