a/regulatory)
> - Batch job alerting - part of the logging and monitoring improvements
> that could be applied to Apache Fineract (we had to connect to BMC suite)
> so then if any job is not running/ending at the scheduled time, the
> operator can check and execute corrective actions.
>
>
egion correct to the
> user settings in the tenant table that would be perfect.
>
> Regards,
>
> -Original Message-
> From: Ádám Sághy
> Sent: Monday, 06 June 2022 10:25 AM
> To: dev@fineract.apache.org
> Cc: Ádám Sághy
> Subject: Re: Timezone issues with Daylight s
: Monday, 06 June 2022 10:25 AM
To: dev@fineract.apache.org
Cc: Ádám Sághy
Subject: Re: Timezone issues with Daylight savings
Hi Sifiso,
I believe by adding and storing the Timezone details of the date time fields in
the database will not have any impact to the user device locale behaviour
Hi All,
My name is Mike and I just joined this community. My previous experience
is in Payroll sofware but we're looking at fineract for a future
project. I would just like to say that from my own experience Date Time
handling is complicated enough as it is that we don't need to make it
any
Ádám - This is an important change to get right, and you've definitely
hit upon an important problem in the current implementation -
inconsistent use of time and failure to use timezones.
It is a simple thing yet "endlessly" complex.
As @Petri Tuomola noted, "The way I’ve seen timezones solved
Hi Sifiso,
I believe by adding and storing the Timezone details of the date time fields in
the database will not have any impact to the user device locale behaviour.
This approach will not change the way of the Fineract is using the user locale
information.
The proposed solution would change
Hi Adam,
Thank you for sharing. Just wanted to know what the impact of having a
server located in a different continent to the user would be? Using this
approach will it pickup the user device's date settings automatically?
-Original Message-
From: Ádám Sághy
Sent: Friday, 03 June
Hi Petri,
Thanks for sharing your thoughts on the subject, it's extremely valuable.
On the changing timezone for a country, we've actually discussed this with
Adam before he proposed the changes and you're right, it could happen for
sure.
The storing everything in UTC. We were struggling with
Hi
Timezones are definitely a “challenge” in every core banking system… it gets
even more fun when you consider all the changes that are being made to
timezones on an infrequent basis: countries changing timezones / timezones
changing offset / countries stopping use of DST etc. The most fun
Hi Adam,
Thanks for bringing attention to this.
Date handling is definitely something we eventually need to take on. The
issue you mentioned around daylight saving and not being able to keep a
strictly monotonic creation date for transactions is definitely concerning.
I agree with your proposal,
10 matches
Mail list logo
