Clojurians Log v2

Hey @itai you can't do nested patching yet, unfortunately, so you'll have to do that work in the app code. We may in the future implement a JSON Merge Patch-style API, per the comments in https://github.com/xtdb/xtdb/pull/3944 > when to nest and when to normalize? The timeless wisdom I often refer to is: normalize until it hurts, denormalize until it works (i.e. runs fast enough). In general I don't think XTDB should be treated too differently to Postgres (etc.), but not having to worry about the number of columns in a table is often quite nice (because XT is columnar, and not row-oriented) It is perhaps worth noting that 6NF (one 'attribute' per table) can make the history more meaningful and simpler to analyse because the changes are more discrete. Another rule of thumb: things that change together should travel together (e.g. live in the same table, or perhaps nested under the same column!)