Bug when deleting a category

[mikev-cw]

When you delete a category used by at least a transaction or a recurring one, an inconsistency is created.

Speaking about recurring transactions, system should avoid this and let the user delete the recurring transaction first.
But what about regular transactions? We should avoid this as well, or let the user "change" the deleted category with a new one?

[napitek]

or perhaps allow transactions without category, or with category “Uncategorized”?
Uncategorized transactions end up in limbo and must be browsed through one by one.
They are obviously not displayed until a category is chosen, except in a designated area

[theperu]

Ideally I would allow the user to choose between two kinds of delete:

• Soft Delete: the category is "marked" as deleted in the db but the previous transactions are still shown with that category.
• Hard Delete: the category is removed from the db but and all the related transactions will change to uncategorized.

In both cases the related budgets and recurring transactions should be deleted and the deleted category should not be visible when the list of categories is displayed.
I would avoid removing the old transactions with a certain category since it might be confusing for the user and it could also make our job harder in the future if we want to optimize the calculation of the net worth or total expenses.