Strange number conversion when using preparedStatement.setLong

Question

Hello all,
I've been working with some code for a while now, and for the most part has been working just fine. As a unique identifier for by objects, I've been using an integer value (int), but have reached the point where I'd like to use a long value.
In creating the table, the type for ID is BIGINT (formerly INTEGER)
      s.executeUpdate("CREATE TABLE Birth_Registry" +
                      "(RUNID INTEGER, " +
                      "ID BIGINT, " +
                      "BIRTHPLACE INTEGER, " +
                      "SEX CHAR, " +
                      "FATHER_ID BIGINT, " +
                      "MOTHER_ID BIGINT, " +
                      "BIRTHDAY DATETIME, " +
                      "primary key(RUNID, ID))");and the preparedStatement looks like:
birthstmt = bcon.prepareStatement(
          "INSERT INTO Birth_Registry VALUES (?, ?, ?, ?, ?, ?, ?)");The actual insertion used to look like (where hom.getID returned an int):
          birthstmt.setInt(1, Core.getRunID());
          birthstmt.setInt(2, hom.getID());
          birthstmt.setInt(3, hom.getBirthplace());
           .  //(more code here filling in other sets)
          birthstmt.addBatch();II've since changed hom.getID to return a long and I now have (for the second line)
birthstmt.setLong(2, hom.getID());-------------
Here's the weird part - using ints, all my numbers convert normally. For example if I have ids 100-110, they show up in the database properly (and uniquely).This still works if I perform an explicit cast, converting the long result of hom.getID() to int (not good programming, but suffices to show a point)
birthstmt.setInt(2, (int) hom.getID())But if I use
birthstmt.setLong(2, hom.getID())I get values like 206158430210 and 210453387505 in the ID field, and duplicates also appear (violating my primary key constraint - which in this case is a good thing).
I'm using SQL Server 2005, Java 1.5_04b5 and have all the latest patches/updates etc. for both. I just can't figure out why changing to setLong leads to such a different number, and if there's something that I can do about it.
Thanks in advance for your help. My only request is for courteous replies - yes I work with Java, but it's not my profession, so I'm trying to do the best I can.

Answer 1

I'm assuming the method you are calling is
PreparedStatement.setLong(int parameterIndex, long x)
this
birthstmt.setLong(2, hom.getID())causes a cast as getID() returns an int?
try
birthstmt.setLong(2, new Integer(hom.getID()).longValue())no casting
Bamkin
Message was edited by:
bamkin-ov-lesta
Think I just read this question the wrong way round ... apologies. Please ignore
I have had problems with casting before and was quick to read this as the problem