Details
-
Bug
-
Resolution: Duplicate
-
Medium
-
None
-
4.2 - EAP
-
4.02
-
Description
The datevalue field of the customfieldvalue table occasionally contains values such as 0008-06-13 10:09:24-05:50:36 which, while technically valid, send JIRA into conniptions and cause pre-upgrade backups to fail with messages such as this:
org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while getting value: (Bad value for type timestamp : 0008-06-1310:09:24-05:50:36) org.postgresql.util.PSQLException: Bad value for type timestamp :0008-06-13 10:09:24-05:50:36 Caused by: java.lang.NumberFormatException: Trailing junk on timestamp: '' at org.postgresql.jdbc2.TimestampUtils.loadCalendar(TimestampUtils.java:226)
Even if we can't do anything about external libraries choking on the retrieve values, can we add some validation logic to ensure the correct value is stored?
Attachments
Issue Links
- duplicates
-
JRASERVER-20117 UI allows entry of invalid dates which causes errors
- Gathering Impact
-
JRASERVER-21366 Cannot index Customfield Datepicker with date < 1970
- Gathering Impact
- relates to
-
JRASERVER-21366 Cannot index Customfield Datepicker with date < 1970
- Gathering Impact