silverstrike

silverstrike copied to clipboard

Currently they are created one after the other. It should however be created atomically. Either all instances are saved or none. We don't want inconsistencies in the db

simhnna

Thinking about multiple users, we might want one system account per user/group to keep all records separate

simhnna

The goal here is to resolve #144, and ensure that there's some general validation on all transaction creation, regardless of api/import/ui creation. This will expose the following errors on transaction...

qedi-r

If you create transactions from other sources, such as the REST API, it's kind of anything goes. There's some rudimentary validation, but having it in the view layer keeps it...

qedi-r