tl;dr
myPreparedStatement.setObject(
… ,
LocalDate.parse(
"23/01/2018" ,
DateTimeFormatter.ofPattern( "dd/MM/uuuu" )
)
) ;
java.time
The modern approach uses the java.time classes that supplanted the terrible Date/Calendar/SimpleDateFormat classes.
The LocalDate class represents a date-only value without time-of-day and without time zone or offset-from-UTC.
Define a formatting pattern to match your input strings.
String input = "23/01/2018" ;
DateTimeFormatter f = DateTimeFormatter.ofPattern( "dd/MM/uuuu" ) ;
LocalDate localDate = LocalDate.parse( input , f ) ;
String output = localDate.toString() ; // Generate text in standard ISO 8601 format.
JDBC 4.2
As of JDBC 4.2, we can exchange java.time objects with the database. Use smart objects rather than dumb text for database interactions.
myPreparedStatement.setObject( … , localDate ) ;
About java.time
The java.time framework is built into Java 8 and later. These classes supplant the troublesome old legacy date-time classes such as java.util.Date, Calendar, & SimpleDateFormat.
The Joda-Time project, now in maintenance mode, advises migration to the java.time classes.
To learn more, see the Oracle Tutorial. And search Stack Overflow for many examples and explanations. Specification is JSR 310.
You may exchange java.time objects directly with your database. Use a JDBC driver compliant with JDBC 4.2 or later. No need for strings, no need for java.sql.* classes.
Where to obtain the java.time classes?
The ThreeTen-Extra project extends java.time with additional classes. This project is a proving ground for possible future additions to java.time. You may find some useful classes here such as Interval, YearWeek, YearQuarter, and more.