Petr Dlouhý

@nitsujri Seems very reasonable. I am not sure, if the `BalanceStatement`s are 100 % prone to rounding errors, but the clean thread safety seems like big benefit. It makes the...

@adamcharnock Ours service has ~1M users, (x2 Hordak accounts), ~13M transactions (x2 legs). Some of the accounts have much larger number of accounts than others, I would expect that maximum...

That SQL function doesn't work very quickly for me. This is `explain analyze` for 1 account: ``` explain analyze SELECT A.id as account_id, L.* FROM hordak_account A INNER JOIN LATERAL...

I don't use any child accounts. I just have 2 accounts for every user and then 3 internal accounts with the in/outband transactions.

@nitsujri Thank you for your contribution. I have tried to update use this code in my project and run the tests with it. I have got lot errors like this:...

@nitsujri Can you please rebase to the current master? I will try to test this again, I expect that I have those errors fixed.

@adamcharnock You are right, that having only few different descriptions would be rather project specific. So yes, I would add it to my TransactionAdmin extension.

I was able to make work sorting with import/export butons just by explicitly setting `change_list_template`: ```python class MyAdmin(ImportExportMixin, SortableAdminMixin, admin.ModelAdmin): change_list_template = "admin/import_export/change_list.html" ``` This seems to be issue of...

There are 3 remaining issues in this library which causes this issue: - The `base_change_list_template` variable should has specific name for each project. I have made [PR for `django-import-export`](https://github.com/django-import-export/django-import-export/pull/1633), but...

@jrief You are right. Those are just warnings, but they are a bit annoying and can hide more serious issues. This simple fix would get rid of them.