| Hi
Your mysql is configured to increase the auto increment values by 2.
if you dont like this behaviour, you might wanna change it to 1.
Regards, Adam Sent from my iPhone On Oct 24, 2023, at 12:03, Kelvin Ikome <kvnik...@gmail.com> wrote:
Hi all,
Thanks for your quick response. Please find details to your responses below.
@Victor I have not been able to replicate this issue as it worked fine on my development environment, together with the UAT environment. I only experience this in OAT and PROD.
@Adam, please find the results below.
Kind regards, Kelvin Hello,
In the m_client table, this behavior will occur when you fill in the creation customer form with an existing value in the database for the mobile_no and external_id columns, because these columns are supposed to have unique data. In this case, MySQL will consider this operation despite the exception raised by fineract. When you correct the operation, you will raise the id jump.
To resolve this in my case, I authorized the database to have the same phone number or external id more than one time. With this MySQL script,
Alter table m_client drop index external_id Alter table m_client drop index mobile_no
Regard
Chantilly Muyaya
Hello,
Is there any way to reproduce the issue? Could you please describe the steps to reproduce this behaviour?
Regards
Victor
Hi devs,
I am experiencing an issue where Fineract generates DB ids which skip through all even numbers (1, 3, 5, 7...). This is present in all certain DB tables (like m_loan, m_client). However, it seems to only be present in certain environments of the deployment but not in all.
Does anyone know what could be causing this or a way to resolve this? Any help/pointers would be greatly appreciated.
Please note, I'm running Fineract 1.8.3 with mysql v8 DB.
Kind regards, Kelvin
|
