V.Narayanan wrote: > Since derby supports Blobs < 2G right now this causes no problems because > 1) when pos <=0 it throws an error > 2) when pos > MAX_INT it rolls around to a negative value and again > throws an exception
Number 2) is not true. Embedded had that issue as well and was just fixed. Long values larger than Integer.MAX_VALUE can be positive or negative when cast to an int. The cast simply truncates the top 32 bits, leaving the sign bit for the int as the 32th bit of the long which can be in any state. Dan.
