Clojurians Log v2

@hlolli thank you. That helps a lot. So I have some general questions regarding om.next ... every application has an app-state atom.. must I have all the things I want to display on screen duplicated into the atom? or can the atom be relatively minimal data and have the queries grab-and-sync with the db? As far as I understand, mutate will change values in the db and when they change they'll automatically (automagically) be updated everywhere they are displayed in the app, true?

@sova you can have it minimal, there's no magic by the way, "painfully" manual the updates after mutation. You need to implement a query that is looking for the change in all the components. If not, you will either lose the data from the compinent or the old state will be cached. About your queston of having things duplicated in a atom, if I understand it correctl, then you can avoid all data duplications if you use normalized app-db levereging the pull syntax for links between the db-tree.

@hlolli thanks! seems like there is quite a bit to learn... someone the other day was trying to help me understand tree->db

... so it's not as straightforward as 1) make a schema & start datomic 2) write component code via (defui) for all the components 3) let it loose. seems like I have to manually keep track of what is changing and what is not ... are there any example applications using a datomic instance that come to mind ?