Date

Attendees

Goals

Discussion items

TimeItemWhoNotes
40 minCheck-insEveryone

Introductions

Check-Ins

For each student please create a new Level 2 entry and enter the following. 

Dylan Robson

Published FINERACT-722 PR.

Added integration test case for JLG top-up loan to verify that the correct member’s previous loan was closed when the top-up loan was disbursed.

Moved forward with FINERACT-723 (about issues with non-IST time zones, because the tenant’s time zone sometimes isn’t considered when creating/calculating dates/times).

Wrote a Bash script (maybe not the best approach, but it was quick, it worked, and I think saved me time in the long run because I re-ran it a few times) to grep recursively for a list of 60 different MySQL date/time functions. I then compiled this list of files where these MySQL date/time functions were found into a spreadsheet. This spreadsheet is 1400 lines long. And each file likely has multiple MySQL date/time function calls.

But there are probably some false positives, because “Date()” is both a MySQL function, and a constructor for the Java Date type. Additionally, many occurrences are .sql migration files, so I don’t know if these are considered problematic by themselves - or if migrations using MySQL date/time functions is just a byproduct of how the given row was originally inserted into its table.

After checking all these files, I need to figure how to translate MySQL date/time functions to use Java date/time in DateUtils. I think this also involves extending DateUtils functionality a bit.

So, I am working my way through this spreadsheet file-by-file to rule out false positives, and to considering solutions using non-SQL date/time functions. 

Continue working through these files and translating MySQL fate/time functions to use the DateUtils class instead, so that dates/times are used in a tenant sensitive way.

Other than the recursive grep for MySQL date/time functions, how else should I look tenant insensitive handling of date/time? Should I also grep for all occurrences of “new Date()” and “new LocalDate()” or something along those lines?

Are these .sql migration files using date/time SQL functions handling date/time insensitively by themselves, or are they only a byproduct of how the row was originally inserted?

What is the purpose of the "joda-time" external library? I see some date/time logic handled there, some handled in MySQL functions, some handled with DateUtils, and some handled with Java Date types only. I need to understand the different purpose of this library compared to DateUtils class.

Yes. I will reach out to the dev mailing list and CC my mentors as usual.

Abhay Chawla

Apoorva K

Supreeth Menon

Cajetan Rodrigues

Moksh Mahajan

Shivansh Tiwari

Saksham Handu

Massabe Lydiane

               * I finished converting all the pages under "Administrations", "Clients, Groups and Centers", "Accounting" and "Configure Notifications" to the gitbook document.

               * I will start updating the pages under "For Operational Users" to the gitbook document.

               * None

               * No

Anshul Singh

Abhijit Ramesh

Prashant Khandelwal

Jivjyot Singh

Ebenezer Graham

Sidhant Gupta

Manish Kumar

Kerlyn Knep

Dundi Raja Vamsi Reddy

Kang Breder


Action items