Ferreteria/v0.41/odata: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
Each node represents the core of a pseudo-record, which can have an arbitrary set of fields (leafs). Each leaf (field within a p-record) must have a unique name. | Each node represents the core of a pseudo-record, which can have an arbitrary set of fields (leafs). Each leaf (field within a p-record) must have a unique name. | ||
* '''concepts''': | * '''concepts''': | ||
** {{l/sub|node}} | ** {{l/sub|node}} - pseudo-record identity | ||
** {{l/sub|leaf}} | ** {{l/sub|leaf}} - field within a pseudo-record | ||
* '''tables''': | * '''tables''': | ||
** {{l/version|sql|node}}: node index | ** {{l/version|sql|node}}: node index | ||
Revision as of 22:09, 16 January 2020
This system is experimental, and replaces/updates the old content system (which was really part of 0.2 or 0.3).
Each node represents the core of a pseudo-record, which can have an arbitrary set of fields (leafs). Each leaf (field within a p-record) must have a unique name.
- concepts:
- tables:
- Template:L/version: node index
- Template:L/version: master node-leaf index
- Template:L/version: leaf type for handling large strings
- Template:L/version: leaf type for handling timestamps