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
Missing transactions in category view #1996
Comments
erf, same issue on |
Also these transactions were previously associated to a budget i removed some days ago. |
Mmm, very strange. It could be mysql related but I am just not sure. I'll have to test. In the mean time, run |
Ok, bug reproduced on FF demo:
The first transaction associated to the |
Thanks for debugging this. It must have taken quite some time to get to the bottom of it. I was able to find the cause. Ultimately, it is because the connection between the deleted budget (still in the database) and the transaction is not severed. But the database query ignores the transaction because it ignores deleted budgets. I've updated the demo site where this should no longer happen. It will be fixed with the next release. Thanks again! |
Glad to help you. Great support once again 👍 |
Bug description
I am running Firefly III version 4.7.9
Some transactions are missing when I open
/categories/show/[catId]/
.They are missing in the transactions table of the view but the transactions exist in db and their amounts are used in the category sum for the month.
See the Decembre total for
/categories/show/17/2018-12-01/2018-12-31
:Here are all transactions find by the search feature on Decembre 2018:
If I edit one of the missing transaction it makes the transaction appearing back in the category view.
Steps to reproduce
Cannot reproduce
Expected behavior
See all transactions for the selected month and the displayed category
Extra info
I have converted my MySQL tables from MyISAM to InnoDB recently. Could it be related ?!
Debug information generated at 2019-01-11 15:25:02 Europe/Paris for Firefly III version 4.7.9.
The text was updated successfully, but these errors were encountered: