... thanks for fixing this Adam... I think this is worth a patch release...
If anyone has something similar in scope then please let me know and we'll add it... otherwise this maintenance release will proceed soon (Monday?). In any case you'll receive the usual messages concerning releases and can chime in any time. Cheers, Aleks On Thu, 8 Dec 2022, 10:47 Ádám Sághy, <[email protected]> wrote: > Dear Community, > > With the release 1.7.0 there were introduced auditing fields for > datatables. > It was using the “CURRENT_TIMESTAMP” SQL function to let the database > engine fill the value for these columns. > > It was touched and changed in 1.8.0 to let the backend provide its value, > however an error was made and instead of the system date of the backend, > the actual tenant date (with tenant timezone) was provided. > > *Example:* > System date: 09:15 8 Dec 2022 (UTC) > Tenant date: 14:45 8 Dec 2022 (+5:30) > > *With 1.7.0* > The auditing datetime was set 09:15 8 Dec 2022 > > *From 1.8.0 (1.8.1, 1.8.2)* > The auditing datetime was set 14:45 8 Dec 2022 > > > The fix is already on the develop branch: > https://issues.apache.org/jira/browse/FINERACT-1828, which fix this to > use the backend system date (similarly as with the rest of the entities). > > Effected releases: > - 1.8.0 > - 1.8.1 > - 1.8.2 > > > If you dont mind lets create a patch release for this! > > > Regards, > Adam Saghy > >
