0041476: API Change: Columns that use the Date reference will only store date part (and not time part) in the database

Openbravo Issue Tracking System - Openbravo ERP

View Issue Details

Project

Category

View Status

Date Submitted

Last Update

0041476

Openbravo ERP

A. Platform

public

2019-07-29 17:03

2019-08-19 09:45

Reporter

AugustoMauch

Assigned To

alostale

Priority

normal

Severity

major

Reproducibility

have not tried

Status

closed

Resolution

invalid

Platform

OS Version

Product Version

Target Version

Fixed in Version

Merge Request Status

Review Assigned To

OBNetwork customer

Web browser

Modules

Core

Support ticket

Regression level

Regression date

Regression introduced in release

Regression introduced by commit

Triggers an Emergency Pack

Summary

0041476: API Change: Columns that use the Date reference will only store date part (and not time part) in the database

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.

Steps To Reproduce

Proposed Solution

Additional Information