Error when save date in SQL database

Question

Hi all,
I try to save a date in to a sql database, but when I run my program I get following error:
Invalid object 11/21/05 9:32 AM of type java.sql.Date assigned to host variable 3.
In my database table I have a fields date (type Data)en time type(Time).
this is the source:
     public void createTitle(int title_id, String description, String user)
          throws SQLException {
          // TODO Auto-generated method stub
          Date date = new Date();
          String dateFormat = "YYYY-MM-DD";
          String timeFormat = "HH:mm:ss";
          SimpleDateFormat ddf = new SimpleDateFormat(dateFormat);
          SimpleDateFormat tdf = new SimpleDateFormat(timeFormat);
          String det = ddf.format(date);
          String creationTime = tdf.format(date);
          PreparedStatement newTitle = conn.prepareStatement("INSERT INTO BE_TITLE (TITLE_ID, DESCRIPTION, DATE_CREATE, TIME_CREATE, USER_CREATE) VALUES (?,?,?,?,?)");     
          try{
               newTitle.setInt(1,title_id);
               newTitle.setString(2,description);
               newTitle.setDate(3, new java.sql.Date(date.getTime()));
               newTitle.setTime(4, new java.sql.Time(date.getTime()));
               newTitle.setString(5, user);
               newTitle.executeUpdate();
          }finally{
               newTitle.close();
Can someone give me a solution for this error
Richard

Answer 1

Hi Richard,
in your application, you atempt to insert a java.sql.Date value into a DATE column, which has non-zero time-components. Open SQL rejects such an atempt.
Please allow me to quote from the OSS message (452727 2004), which Detlev refers to in his quote:
<i>
about one year ago, we had a very lengthy discussion on this issue - not only internally at SAP but also with Jonathan Bruce, the specification lead for JBDC at Sun.                                                                               
We have the following dillema:                                                                               
The javadoc of the constructor java.sql.Date(long) states:                                                                               
"If the given milliseconds value contains time information, the driver will set the time components to the time in the default time zone (the time zone of the Java virtual machine running the application) that corresponds to zero GMT."                                                                               
With Jonathan Bruce, we tried to clarify when this normalization should take place.                                                               
1) Source code inspection shows that it is not the class java.sql.Date the performs the normalization.                                                                               
2) The Javadoc states that the JDBC driver should perform the             
normalization. If it is the driver, more open questions arrise:                                                                               
a) When shall the normalization be performed?                             
   - if a setDate method is invoked?                                      
   - only for INSERT and update statements or also for all other parameters?                                                               
   - shall the getDate method perform the normalization?                  
   - what about set/getObject?                                            
   - the java Docs of set/getDate don't tell anything about normalization.                                                            
   - according to which time zone shall the value be normalized?          
     - UTC                                                                
     - vm time zone?                                                      
     - database time zone?                                                                               
3) If an automatic normalization is performed, data will be modified upon insertion (or extraction) from the database. This means that we cannot quarantee if we insert and Date object retrieve it again that the two objects will be equal.
In the discussion with Jonathan, we couldn't clarify the issue. However, Jonathan promised that the JDK should be modified in such a way that the JDK is responsible for the normalization. (So far such a change has not been done).                                                                               
In order to be on the safe side, SAP chose that Open SQL should reject any Date values that are not normalized. This is what we have          
implemented and documented. I agree, that in this repect, Open SQL is stricter than the JDBC standard demands.                                                                               
To help the application with the task to normalize a Date (and Time) object, we offer the helper class                                      
com.sap.sql.DateTimeNormalizer which you find in opensql.jar.                                                                               
To come to a conclusion, the bevavoir you observed is from our side not a bug of Open SQL but a feature. Please use DateTimeNormalizer to normalize Date objects appropriately.                                  
</i>
I hope, you can follow our reasoning.
Best regards,
Adrian