-
Notifications
You must be signed in to change notification settings - Fork 190
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Huge data loss when creating a new account with the same name #1988
Comments
I also changed the new account to the checking type of the original one, but it didn't bring back all the records |
Hi, @aardbol this is indeed a bug when handling the constraint conflict (here is the account name). for this particular case, we can restore the previous account if you can share your database. |
While I appreciate the assistance, sharing the db is not an option. I assume I just have to make the modification via a db application that supports sqllite? |
Exactly. find the account ID from the transaction list and re-create it via any sqlite cli. |
v2024.12.22 (1054) will fix this, you can try it out via https://play.google.com/apps/testing/com.money.manager.ex.android |
Sounds great. When will the release apk be on github? That's my way of installation |
There's no apk |
Ops @guanlisheng can you update? |
done. i thought guys can install it from google play
|
Describe the bug
This is as critical as my previous issue #1827. When creating a new account with the same name as another one, the previous one disappears from the favorite account list and eventually from the list of accounts after a restart. I can't seem to get that account back and all records seem to have been lost.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
both accounts exist with the same name because the account type is different, or prevent a new account with the same name from being created by showing an error
Screenshots
If applicable, add screenshots to help explain your problem.
Device Information:
The text was updated successfully, but these errors were encountered: