You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Handling of empty String to "empty" Timestamp is indeed unfortunate and shouldn't occur.
If nothing else works you could alternatively add/override setTimestamp(Timestamp ts) method and look if underlying epoch value (long) is 0L and if so translate instance into null.
ps. which Timestamp class are we talking about? java.sql.Timestamp?
FWTW, I think this is unfortunately something that happens, as jackson-databind has TimestampDeserializer that indicates that so-called "empty" value is one with instance constructed with timestamp of 0L -- which means January 1st, 1970, UTC (epoch).
Hi.
From version 2.12.0 deserialization timestamps works in other way.
I have field in model:
In response i receive something like this:
Earlier this assertion worked fine:
Assert.assertNull(response.getData());
On the newest version 2.14 deserialization returns something like this:
Actual :1970-01-01 01:00:00.0
Is it possible to return null again when I try deserialize empty field to Timestamp?
The text was updated successfully, but these errors were encountered: