Well, I think first you should look up what a "bigint" means for your specific database type (because different languages can have their own definition of numerical value), and next you need to compare it to the Java numeric types.
There is no need to declare any of those values as Long.Sorted out by autoboxing. Search this forum; there are threads about wrapper classes and boxing active at the moment.
But be careful about BigInts; they can be marked unsigned. I do not know what will happen to values ≥ 9,223,372,036,854,775,808. Maybe they will be converted to negative values since long is a two's complement type. But I am not at all sure; try it. It doesn't say in the documentation for the ResultSet method.
Campbell Ritchie wrote:There is no need to declare any of those values as Long.
Except if the field can be NULL in the database. You could try using a value like -1, 0 or Long.MIN_VALUE instead of a null Long, but only if you're 100% sure that these values will never be actual values in the database.