Vaibhav Gargs wrote:So, why JDBC was not designed to deal with java.util.date? Why there were two classes initially: java.util.date/java.sql.date?
API documentation wrote:To conform with the definition of SQL DATE, the millisecond values wrapped by a java.sql.Date instance must be 'normalized' by setting the hours, minutes, seconds, and milliseconds to zero in the particular time zone with which the instance is associated.
Stephan van Hulst wrote:
The java.sql APIs could be improved with default methods that accept java.time objects. Maybe they will do that in the future.
Dave Tolls wrote:Oh yes. I live in hope, but I'm not holding my breath, considering JDBC is only a set of interfaces, and it's everyone else who produce the actual drivers that would end up doing the work.
You mean put it out of its misery?Stephan van Hulst wrote:. . . they chose to abandon it completely in favor of the java.time API. . . .
Don't get me started about those stupid light bulbs. |