How to get current timestamp in string format in Java? "yyyy.MM.dd.HH.mm.ss"

Question

How to get timestamp in string format in Java? "yyyy.MM.dd.HH.mm.ss"

String timeStamp = new SimpleDateFormat("yyyy.MM.dd.HH.mm.ss").format(new Timestamp());

This is what I have, but Timestamp() requires an parameters...

Corycorybant

preparedStatement.setTimestamp(1, new Timestamp(System.currentTimeMillis())); – Canzonet

What error are you getting? – Coolidge

FYI, the terribly troublesome old date-time classes such as SimpleDateFormat and java.sql.Timestamp are now legacy, supplanted by the java.time classes built into Java 8 and later. See Tutorial by Oracle. – Frankhouse

Answer 1

Replace

new Timestamp();

with

new java.util.Date()

because there is no default constructor for Timestamp, or you can do it with the method:

new Timestamp(System.currentTimeMillis());

Adrianadriana

FYI, the terribly troublesome old date-time classes such as java.util.Date and java.sql.Timestamp are now legacy, supplanted by the java.time classes built into Java 8 and later. See Tutorial by Oracle. – Frankhouse

I used: new Date().getTime(); – Meticulous

Answer 2

Use java.util.Date class instead of Timestamp.

String timeStamp = new SimpleDateFormat("yyyy.MM.dd.HH.mm.ss").format(new java.util.Date());

This will get you the current date in the format specified.

Sigmoid

This helped me out and I made some changed so I don't have to import new java.text.SimpleDateFormat("dd/MM/yyyy HH:mm:ss").format(new java.util.Date()) – Guerdon

Better new SimpleDateFormat("yyyy.MM.dd HH:mm:ss").format(new Date()); – Leisured

SimpleDadeFormat is not thread safe, make sure you are not using it in multithreading environment. Once I overlooked this and it was giving unpredictable results when two dates were compared. – Byssus

Answer 3

tl;dr

Use only modern java.time classes. Never use the terrible legacy classes such as SimpleDateFormat, Date, or java.sql.Timestamp.

ZonedDateTime                    // Represent a moment as perceived in the wall-clock time used by the people of a particular region ( a time zone).
.now(                            // Capture the current moment.
    ZoneId.of( "Africa/Tunis" )  // Specify the time zone using proper Continent/Region name. Never use 3-4 character pseudo-zones such as PDT, EST, IST. 
)                                // Returns a `ZonedDateTime` object. 
.format(                         // Generate a `String` object containing text representing the value of our date-time object. 
    DateTimeFormatter.ofPattern( "uuuu.MM.dd.HH.mm.ss" )
)                                // Returns a `String`. 

Or use the JVM’s current default time zone.

ZonedDateTime
.now( ZoneId.systemDefault() )
.format( DateTimeFormatter.ofPattern( "uuuu.MM.dd.HH.mm.ss" ) )

java.time & JDBC 4.2

The modern approach uses the java.time classes as seen above.

If your JDBC driver complies with JDBC 4.2, you can directly exchange java.time objects with the database. Use PreparedStatement::setObject and ResultSet::getObject.

Use java.sql only for drivers before JDBC 4.2

If your JDBC driver does not yet comply with JDBC 4.2 for support of java.time types, you must fall back to using the java.sql classes.

Storing data.

OffsetDateTime odt = OffsetDateTime.now( ZoneOffset.UTC ) ;  // Capture the current moment in UTC.
myPreparedStatement.setObject( … , odt ) ;

Retrieving data.

OffsetDateTime odt = myResultSet.getObject( … , OffsetDateTime.class ) ;

The java.sql types, such as java.sql.Timestamp, should only be used for transfer in and out of the database. Immediately convert to java.time types in Java 8 and later.

java.time.Instant

A java.sql.Timestamp maps to a java.time.Instant, a moment on the timeline in UTC. Notice the new conversion method toInstant added to the old class.

java.sql.Timestamp ts = myResultSet.getTimestamp( … );
Instant instant = ts.toInstant(); 

Time Zone

Apply the desired/expected time zone (ZoneId) to get a ZonedDateTime.

ZoneId zoneId = ZoneId.of( "America/Montreal" );
ZonedDateTime zdt = ZonedDateTime.ofInstant( instant , zoneId );

Formatted Strings

Use a DateTimeFormatter to generate your string. The pattern codes are similar to those of java.text.SimpleDateFormat but not exactly, so read the doc carefully.

DateTimeFormatter formatter = DateTimeFormatter.ofPattern( "uuuu.MM.dd.HH.mm.ss" );
String output = zdt.format( formatter );

This particular format is ambiguous as to its exact meaning as it lacks any indication of offset-from-UTC or time zone.

ISO 8601

If you have any say in the matter, I suggest you consider using standard ISO 8601 formats rather than rolling your own. The standard format is quite similar to yours. For example:
2016-02-20T03:26:32+05:30.

The java.time classes use these standard formats by default, so no need to specify a pattern. The ZonedDateTime class extends the standard format by appending the name of the time zone (a wise improvement).

String output = zdt.toString(); // Example: 2007-12-03T10:15:30+01:00[Europe/Paris]

Convert to java.sql

You can convert from java.time back to java.sql.Timestamp. Extract an Instant from the ZonedDateTime.

New methods have been added to the old classes to facilitate converting to/from java.time classes.

java.sql.Timestamp ts = java.sql.Timestamp.from( zdt.toInstant() );

---

---

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?

• Java SE 8, Java SE 9, Java SE 10, Java SE 11, and later - Part of the standard Java API with a bundled implementation.
• Java 9 adds some minor features and fixes.
• Java SE 6 and Java SE 7
• Most of the java.time functionality is back-ported to Java 6 & 7 in ThreeTen-Backport.
• Android
• Later versions of Android bundle implementations of the java.time classes.
• For earlier Android (<26), the ThreeTenABP project adapts ThreeTen-Backport (mentioned above). See How to use ThreeTenABP….

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.

Frankhouse

So what is The Right Way to get the current wall clock time stamp in format "yyyy.MM.dd.HH.mm.ss"? Without explicitly specifying hard-coded string of my local time zone? That's what topic starter was asking, and I could not find it in your answer... – Denisse

@Denisse I added a line of example code to the tl;dr section showing how to ask explicitly for the JVM’s current default time zone. Calling `now()‘ without any arguments does the same but is not clear if you meant to use the default or if you were ignorant or forgetful about the crucial issue of time zone. – Frankhouse

@BasilBourque very compact and pure +1. – Mouthpart

Answer 4

Use modern java.time classes if you use java 8 or newer.

String s = DateTimeFormatter.ofPattern("yyyy-MM-dd HH:mm:ss").format(LocalDateTime.now());

---

Basil Bourque's answer is pretty good. But it's too long. Many people would have no patience to read it. Top 3 answers are too old and may mislead Java new bee .So I provide this short and modern answer for new coming devs. Hope this answer can reduce usage of terrible SimpleDateFormat.

Foxe

Answer 5

You can make use of java.util.Date instead of Timestamp :

String timeStamp = new SimpleDateFormat("yyyy.MM.dd.HH.mm.ss").format(new Date());

Moffat

Answer 6

You can use the following:

new java.sql.Timestamp(System.currentTimeMillis()).getTime()

Result:

1539594988651

Berlinda

It doesn’t have the string format asked for. Also I’m afraid that the only thing it adds to a couple of similar answers, is needless complication… – Archuleta

Answer 7

A more appropriate approach is to specify a Locale region as a parameter in the constructor. The example below uses a US Locale region. Date formatting is locale-sensitive and uses the Locale to tailor information relative to the customs and conventions of the user's region Locale (Java Platform SE 7)

String timeStamp = new SimpleDateFormat("yyyy.MM.dd.HH.mm.ss", Locale.US).format(new Date());

Ridgeling

No such thing as “Locale Zone”. I suspect your are confusing Locale and time zone which are unrelated. Locale controls the cultural norms for formatting and the human language used for name of month/day. The time zone adjusts the date-time representation to be appropriate to some region’s wall-clock time. In the case of this Question, Locale is irrelevant as there are no formatting issues with which to apply cultural norms nor are there any names of month/day to localize to any particular human language. – Frankhouse

@BasilBourque Thank you for your input. I've updated the answer to be more explicit – Ridgeling

Answer 8

I am Using this

String timeStamp = new SimpleDateFormat("dd/MM/yyyy_HH:mm:ss").format(Calendar.getInstance().getTime());
System.out.println(timeStamp);

Nylon

This was the only answer, which I was actually able to use. I was able to find proper imports! – Nobell

Answer 9

Use the following strategy.

import java.sql.Timestamp;

Timestamp today = new Timestamp(System.currentTimeMillis())


 

Rave

It does not answer the question asked. And using the Timestamp class is not recommended. It’s a very poorly designed class and long outdated. Use java.time. See the answer by Basil Bourque. – Archuleta

Also it’s already proposed in two existing answers including the accepted one. – Archuleta

Answer 10

java.time

Those java.util.Date answers at the top need to go. Here's some code I wrote that deals with different formats. It's also easier to go with a working example:

package com.brian.TimeZoneUtil;

import java.time.*;
import java.time.format.*;
import java.time.LocalDateTime;

public class TimeZoneConversion {


        public static void main(String[] args) {
            
            String inSlashDateString = "10/31/201100:00:00";
            String inHyphenDateString = "2011-10-31T01:01:01";
            String inEpochDateString = "1687170164410";

            DateTimeFormatter slashFormatter = DateTimeFormatter.ofPattern("MM/dd/yyyyHH:mm:ss");
            DateTimeFormatter hyphenFormatter = DateTimeFormatter.ofPattern("yyyy-MM-dd'T'HH:mm:ss");
            
            ZonedDateTime epochDateTime = Instant.ofEpochMilli(Long.parseLong(inEpochDateString)).atZone(ZoneId.of("America/Indiana/Indianapolis"));
            
            System.out.println(DateTimeFormatter.ofPattern("yyyyMMdd HH:mm:ss").format( LocalDateTime.parse(inSlashDateString + "00:00:00", slashFormatter)));
            System.out.println(DateTimeFormatter.ofPattern("yyyyMMdd HH:mm:ss").format( LocalDateTime.parse(inHyphenDateString, hyphenFormatter)));
            System.out.println(epochDateTime.format(DateTimeFormatter.ofPattern("yyyyMMdd HH:mm:ss")));
            
                        
        }
}

Traceetracer

No need to define this pattern: "yyyy-MM-dd'T'HH:mm:ss". Already defined: ISO_LOCAL_DATE_TIME. – Frankhouse