On 2016-08-16 12:25, Tomek Rekawek wrote:
Hello,
I was wondering whether it’d make sense to normalise the RDB Document Store
schema - get rid of the JSON/JSOP concatenated strings and store each key/value
in a separate database row. Something like this:
id STRING
key STRING
Hi Tomek,
I like the idea of revisiting our current schema based on usage so
far. However couple of points around potential issue with such a
normalized approach
- This approach would lead to a thin and lng table. As noted in
[1] in a small repo ~14 M nodes we have ~26 M properties. With
Hi Tomek,
While at first glance I like the idea of normalizing the schema, but
there are potential practical issues with the approach:
* It'd incur a very heavy migration impact on upgrade or RDB setups -
that, most probably, would translate to us having to support both
schemas. I don't feel that
Hello,
I was wondering whether it’d make sense to normalise the RDB Document Store
schema - get rid of the JSON/JSOP concatenated strings and store each key/value
in a separate database row. Something like this:
id STRING
key STRING
revisionSTRING (nullable)
value
