(cloud) experimental approach to ensure the ledgers do not get out of sync
This commit is contained in:
@@ -1,8 +1,13 @@
|
||||
* try again to see if we can get upsert-ledger into the same transaction, making it all or nothing
|
||||
* look for all usages of transact-with-ledger
|
||||
* propose-invoice should use upsert invoice as well
|
||||
|
||||
it looks like there are a bbunch of orrphaned customizations for accounts, breaking indexes
|
||||
upsertledger - matching transaction rule might not assign an account. Other things might not assign accounts. This is an assertion that is commented out. Determine consequence of disabling
|
||||
Double check each job still functions in the new system
|
||||
Make reports just be based on running-balances
|
||||
Test exports
|
||||
Move pay into iol-ion.tx, make sure to use upsert-invoice
|
||||
|
||||
Some jobs just aren't so big they need to be jobs anymore:
|
||||
Refreshing running balance for journal entry lines
|
||||
@@ -12,7 +17,6 @@ Closing auto invoices
|
||||
|
||||
Running Balance Cache
|
||||
* Add tests for upsert-ledger
|
||||
* try again to see if we can get upsert-ledger into the same transaction, making it all or nothing
|
||||
* Make a new way to reset the entire cache for a client
|
||||
|
||||
Address memory
|
||||
|
||||
Reference in New Issue
Block a user