Ferreteria/v0.42/odata: Difference between revisions
No edit summary |
m (corrected page name) |
||
| Line 6: | Line 6: | ||
* '''tables''': | * '''tables''': | ||
** {{l/version|sql|node}}: core pseudorecord | ** {{l/version|sql|node}}: core pseudorecord | ||
** {{l/version|sql| | ** {{l/version|sql|node_leaf}}: field within a pseudorecord | ||
==Background== | ==Background== | ||
This system is experimental, and replaces/updates the old [[Ferreteria/modules/content|content system]] (which was really part of 0.2 or 0.3). It's a simplification of [[Ferreteria/v0.41/odata|v0.41]], which was designed as far as schema and some code but ran into coding difficulties when trying to use the system for event logging. The problems were solvable, but a simpler design seemed like it would represent much less technical debt. | This system is experimental, and replaces/updates the old [[Ferreteria/modules/content|content system]] (which was really part of 0.2 or 0.3). It's a simplification of [[Ferreteria/v0.41/odata|v0.41]], which was designed as far as schema and some code but ran into coding difficulties when trying to use the system for event logging. The problems were solvable, but a simpler design seemed like it would represent much less technical debt. | ||
Revision as of 15:32, 25 January 2020
About
Each Template:L/version represents the core of a pseudo-record, which can have an arbitrary set of fields (leafs). Each Template:L/version (field within a p-record) must have a unique name.
There is a registry, maintained by code, of pseudorecord types (node.Type). This is so the code can look up the proper class to use for handling each node (pseudorecord). It remains to be seen if this part works as envisioned.
Pages
- tables:
- Template:L/version: core pseudorecord
- Template:L/version: field within a pseudorecord
Background
This system is experimental, and replaces/updates the old content system (which was really part of 0.2 or 0.3). It's a simplification of v0.41, which was designed as far as schema and some code but ran into coding difficulties when trying to use the system for event logging. The problems were solvable, but a simpler design seemed like it would represent much less technical debt.