[WIP] Multiple categories per transaction

[tufteddeer]

As suggested in #39, it would be nice if we could add more than one category to a transaction.

It's still wip, feedback and thoughts very much appreciated!

[tufteddeer]

A (not very pretty) screenshot of 3dda80f:

[tufteddeer]

Right now transactions are saved one time for each category, so there is no need to mess with all the transaction models, overviews and stuff.

[tufteddeer]

@AndreAle94 i would like to continue hacking on this feature if you are okay with the way I'm implementing it, so a little feedback would be appreciated (nothing fancy, just your general impression) 😃

[AndreAle94]

Hello, thanks for the contribution. I think it's a good workaround for the moment. However, I don't think it's the best way to implement this feature, so I don't think I will merge this changes into the repository. Managing split transactions in this way can work when a transaction is created, not when the user wants to correct / change something or delete it. Moreover, the transaction list can easily become confusing. The best way in my opinion (but it requires a lot of work both in structuring the db and in modifying all existing queries) is to create an ad hoc structure in the database and manage these transactions as part of a group. These changes must then be reflected throughout the backup file structure. This is why they have not yet been implemented.

[tufteddeer]

I agree, that's what i expected. Remodeling the storage backend is too much for me right now but if there's a way to help implementing this feature, I'd like to.