Project:
| View Revisions: Issue #41476 | [ All Revisions ] [ Back to Issue ] | ||
| Summary | 0041476: API Change: Columns that use the Date reference will only store date part (and not time part) in the database | ||
| Revision | 2019-07-29 17:05 by AugustoMauch | ||
| Description | The current behaviour of columns that use the Date reference is the following: - When saving a record from the ERP, the incoming date value has the YYYY-MM-DD format, and the data is stored with 00:00:00 as the time part. - When the value is programatically set (i.e. order.setOrderDate(new Date()) ), then both the date and the time part of the given date will be stored in the database. The proposed change is to automatically strip the time part for values used in columns that use the Date reference. Impact: Only those flows that were programatically setting dates with a time part, and then retrieving the store date and using the time part would be affected. Those affected should use the DateTime reference instead. |
||
| Revision | 2019-07-29 17:03 by AugustoMauch | ||
| Description | The current behaviour of columns that use the Date reference is the following: - When saving a record from the ERP, the incoming date value has the YYYY-MM-DD format, and the data is stored with 00:00:00 as the time part. - When the value is programatically set (i.e. order.setOrderDate(new Date()) ), then both the date and the time part of the given date will be stored in the database. The proposed change is to automatically strip the time part for values used in columns that use the Date reference. |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |