Hello, (Forwarding as the original message doesn't seem to make it to the list)
Regards, Wojtek ---- This patch fixes the problem when using CallableStatementSapDB.setObject ( index, object, type ) with type = Types.DATE or Types.TIME or Types.TIMESTAMP. Unpatched version didn't work correctly (exception: invalid timestamp format: ISO), because of timezone included in Timestamp (and SapDB does not support timezones in timestamp values). The second fix makes setTimestamp (index,timestamp) and setTimestamp (index,timestamp,calendar) coherent and working properly. Unpatched implementation of 2-parameter setTimestamp did not work correctly (the same reason as above) -- Marek (See attached file: CallableStatementSapDB.java.diff)
CallableStatementSapDB.java.diff
Description: Binary data
