Does this java parameter would insert a row into sql server?

I have Java code that I want to test on SQL server if it would insert a row. Currently, I don't have a tool to test this code yet. Here is the code:

MapSqlParameterSource parameters = new MapSqlParameterSource();
parameters.addValue("id", "1"); // primary key
parameters.addValue("date", new GregorianCalendar(TimeZone.getTimeZone("America/New_York").getInstance().getTimeInMillis()); // Calendar object for date
return parameters;

and SQL Server table would be something like id with INTEGER and date with DATETIME2 (this must be DATETIME2).

I would like to know if this would insert a row.

Problem I'm having: I have this code which currently works with Oracle database. I am using HSQLDB to test it on my unit test by creating duplicate table with same column and data type. Now, I need to migrate database from Oracle to SQL Server. As a process, I am making the project compatible for both Oracle and SQL Server without writing separate code.

In my new unit test, I use HSQLDB to create table and columns. For some reason, HSQLDB throws org.hsqldb.HsqlException: data exception: invalid datetime format error when this Calendar type is passed in as parameter. I want to make sure if this problem is from HSQLDB or SQL Server.

It's a problem with the JDBC driver, but I wouldn't blame it overly much; Calendar is horrible API, and obsolete to boot. Don't use it.

The 'safest' date/time type to send is an instance of java.sql.Timestamp. The 'best' date/time type to send is something from the java.time package, preferably a ZonedDateTime. If your JDBC driver lets you do that, do that. If it does not, grumble, grit your teeth, fire off a bug report with the JDBC driver maker, and use java.sql.Timestamp.

Your code tries to assign a Long value to a (JDBC) TIMESTAMP column. Setting a long (or Long) value on a TIMESTAMP column is not defined in JDBC. If this works in Oracle, then that is a non-standard extension specific to the Oracle driver, and therefor is not guaranteed to work in other drivers.

You will need to use the types that are defined by JDBC. For a TIMESTAMP (without time zone) column, the JDBC 4.3 specification only defines support for the following Java types:

• java.sql.Timestamp (primary type, but recommendation is to use java.time.LocalDateTime instead)
• java.lang.String
• java.sql.Date (recommendation is to use java.time.LocalDate instead)
• java.sql.Time (recommendation is to use java.time.LocalTime instead)
• java.util.Calendar (though I'm not sure if this is commonly supported)
• java.util.Date (though I'm not sure if this is commonly supported)
• java.time.LocalDate (introduced in JDBC 4.2)
• java.time.LocalTime (introduced in JDBC 4.2)
• java.time.LocalDateTime (introduced in JDBC 4.2)