java.util.date

java.util.Date是在除了SQL语句的情况下面使用的。 java.sql.Date是针对SQL语句使用的，它只包含日期而没有时间部分 它 们都有getTime方法返回毫秒数，自然就可以直接构建。 java.util.Date 是 java.sql.Date 的父类，前者是常用的表示时间的类，我们通常格式化或者得到当前时间都是用他，后者之后在读写数据库的时候用他，因为PreparedStament的 setDate()的第2参数和ResultSet的getDate()方法的第2个参数都是java.sql.Date。 java.sql.Date转为java.util.Date java.sql.Date date=new java.sql.Date(); java.util.Date d=new java.util.Date (date.getTime()); java.util.Date转为java.sql.Date java.util.Date utilDate=new Date(); java.sql.Date sqlDate=new java.sql.Date(utilDate.getTime()); java.util.Date utilDate=new Date(); java.sql.Date sqlDate=new java.sql.Date(utilDate

I wanted to convert from string to java.util.Date. for the same purpose I used following code, String timeStamp = "Mon Feb 14 18:15:39 IST 2011"; DateFormat formatter = new SimpleDateFormat("dow mon dd hh:mm:ss zzz yyyy"); Date ts = (Date)formatter.parse(timeStamp); The format given to SimpleDateFormat() is format of java.util.Date. When you convert util's Date to string it comes in this format('dow mon dd hh:mm:ss zzz yyyy'). But when I execute code, It gives me Exception. I Don't know what exactly I needed to do to get rid of this problem. I am posting the part of StackTrace of exception. If

In java.util.Date : * In all methods of class <code>Date</code> that accept or return * year, month, date, hours, minutes, and seconds values, the * following representations are used: * <ul> * <li>A year <i>y</i> is represented by the integer * <i>y</i><code>-1900</code>. Of course, in Java 1.1, the getYear() method and the like were deprecated in favor of java.util.Calendar , which still has this weird deprecation note: int getYear() Deprecated. As of JDK version 1.1, replaced by Calendar.get(Calendar.YEAR) - 1900. setYear(int year) Deprecated. As of JDK version 1.1, replaced by Calendar.set

It seems that the new java.time API offers everything from java.util.Date and much more. Is there any reason to use java.util.Date when the newer java.time API is there since Java 8? Should java.util.Date and java.util.Calendar be avoided completely? Short answer: The new API java.time is way better than the old world with java.util.Date and java.util.Calendar . So yes, the new API should be preferred in new code. For a quick overview: Once I had written a comparison of features in table form for various date-time-libraries. There is almost no feature which java.time is missing but exists in

And wait, don't rush to answer "java.util.Date", consider the following scenario. Person object having 2 fields: "birthday" and "nextMeeting" both java.util.Date. Now birthday stored in database as date type column (no time) for eg. 01-10-1979, and nextMeeting as datetime type for ex. 01-10-2010 20:00:00. You pull it from db, "birthday" will be auto set to midnight by JDBC. Now you need to send this object to other JVM using lets say RMI or whatever technology. On the other end JVM has timezone -1h from originating JVM. This is where problem starts. nextMeeting become 01-10-2010 19:00:00 which