Browse Source
there were a bug were the currency exchange settings was never saved DB: is a too tricky pattern that we'll drop in the future. the problem with this is that we actually miss cases where a DB: should be triggered ultimately an action should be atomic and each changes it affect should be saved without extra magic for performance purpose we can just === check if things have actually changed and we can do this at many levels in the future, we will try to reorganize things to allow this better, for instance splitting latest countervalues vs historical countervalues so you only save the latest more frequently..master
Gaëtan Renaudeau
7 years ago
2 changed files with 22 additions and 18 deletions
Loading…
Reference in new issue