-
MODX Staff
- 10,725 Posts
Upcoming releases will have a full set of audit metadata for any and all user-editable objects (i.e. Documents, Snippets, Chunks, TVs, Plugins, Modules, etc.), but this will be externalized, in separate tables, and is directly related to the versioning concepts that will accompany these changes. In addition to being relevant to versioning, this will also address the problem of TV’s only having a record if the value is different than the default (and resetting it to default deletes the row), as well as to reduce the impact of the audit data on SQL access when it is not relevant (i.e. keeps the TV or other source table compact and efficient).
I would suggest adding a separate table that tracks whatever additional data you want by templatevar id and content id, and you will protect your upgrade path while still achieving what you need to. You can then use plugins to make sure that data is created, updated, or loaded when appropriate in the front-end and back-end.
I appreciate the response. I’ll probably end up creating another table, as you suggested.