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
Just to confirm, the title of this issue states that you're expecting the current date. I'm thinking that it should be null instead of epoch when the parameter type is not a date. Is there a reason not to go this route?
I agree with Michael, null is a better default value than the suggested current date or the start of epoch date (as implemented currently). I just checked all DDLs and they all declare the DATE_VAL column to be nullable by default. So changing new Timestamp(0L) with null in JdbcJobExecutionDao#insertParameter should be safe.
Sonali Singhal opened BATCH-2015 and commented
Affects: 2.1.8
0 votes, 5 watchers
The text was updated successfully, but these errors were encountered: