You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fineract.apache.org by "Adam Saghy (Jira)" <ji...@apache.org> on 2022/12/08 09:27:00 UTC
[jira] (FINERACT-1828) Wrong audit time is set for datatables
[ https://issues.apache.org/jira/browse/FINERACT-1828 ]
Adam Saghy deleted comment on FINERACT-1828:
--------------------------------------
was (Author: adamsaghy):
[https://github.com/apache/fineract/pull/2792]
> Wrong audit time is set for datatables
> --------------------------------------
>
> Key: FINERACT-1828
> URL: https://issues.apache.org/jira/browse/FINERACT-1828
> Project: Apache Fineract
> Issue Type: Bug
> Affects Versions: 1.8.0, 1.8.1, 1.8.2
> Reporter: Adam Saghy
> Assignee: Adam Saghy
> Priority: Major
>
> During the Business date refactor:
> Business date - part 2 (#2384)
> commit hash: 632a08a5
> Date: on 29/06/2022 at 15:56
> Priorly the database engine was used to generate value for this columns:
> "CURRENT_TIMESTAMP"
> During the above refactor we were moving away to not let the DB engine to set the value, rather the fineract backend set it explicitly.
> However wrong value was set, instead of the system time (server time), which was used majorly for other entities, the actual tenant time was set here.
> This story is about to fix this!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)