- Issue created by @alorenc
- 🇷🇴Romania claudiu.cristea Arad 🇷🇴
Just a short history: I was very hesitant to use a JSON field for many reasons. Unified syntax, support across different types of relational DBs (I think MariaDB still has no support for indexing). For the sake of having a single table I went with this solution. But the initial design was to add a serial in track_usage then have a 2nd table, say track_usage_paths with
tid: ref to track_usage serial field
path (int): 0..N
delta (int): 0..N position within one path
type: entity type
id: entity id
revision: - 🇷🇴Romania claudiu.cristea Arad 🇷🇴
We close this as duplicate of 📌 Replace JSON column with normalized table structure Active . We will provide there a better solution.