Dear All

I was just looking up the source code of the jTDS driver.
It seems that it is trashing the heap with java.lang
wrapper classes, even when one is using only primitive
types in his application.

For example, when I am doing, whereas the column
is integer:

   ResultSet set;
   set.getLong(1);

This amounts to a call to:

    public long getLong(int columnIndex) throws SQLException {
         return ((Long) Support.convert(con, getColumn(columnIndex),

                  java.sql.Types.BIGINT, null)).longValue();
    }

During the above call a Long object will be created, as
can be seen from the convert implementation:

    case java.sql.Types.BIGINT:
      if (x == null) {
        return LONG_ZERO;
      } else if (x instanceof Long) {
        return x;
      } else if (x instanceof Byte) {
        return new Long(((Byte)x).byteValue() & 0xFF);
      } else if (x instanceof Number) {
        return new Long(((Number) x).longValue());
      } else if (x instanceof String) {
        return new Long(((String) x).trim());
      } else if (x instanceof Boolean) {
        return ((Boolean) x).booleanValue() ? LONG_ONE : LONG_ZERO;
      }
      break;

A solution would be to do the following
call on the result set:

   (long)set.getInt(1);

But what if I want to make the code, lets say column
size independent, and want to use a getLong() call
only.

Does this trashing happen in every JDBC driver?
Are there alternatives to jTDS, when accessing
MS SQL Databases?

Best Regards