Hello
I want to create a db table for capturing snapshots of Udt, Udt Instances, and Atomic tag configurations that can be referenced by our other tables - to be able to manage version history on tag config changes among various other internal uses that will require us to reference a tag config snapshot as opposed to the current config.
To maximise compatability with any future ignition versions I wanted to base my table off the internal TAGCONFIG table design - and had a question for the devs regarding the purpose / reason behind some of the tags having compound uuids (uuid.uuid) ? Is this something that was needed due to a limitation on the current table schema? Or is it for some sort of optimisation?