Ferreteria/v0.5/node: Difference between revisions

From Woozle Writes Code
Jump to navigation Jump to search
No edit summary
No edit summary
 
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
'''versions''': {{l/ferreteria/|v0.41/odata|0.41}}, {{l/ferreteria/|v0.42/odata|0.42}}, {{l/ferreteria/|v0.5/node|0.5}}
'''versions''': {{l/ferreteria/|v0.41/odata|0.41}}, {{l/ferreteria/|v0.42/odata|0.42}}, {{l/ferreteria/|v0.5/node|0.5}}
==About==
==About==
The nodes subsystem is built from a set of tables working together.
The nodes subsystem stores arbitrary hierarchical data within a standard relational database.
 
The current proof-of-concept implementation stores all data using only one table, but this can easily be optimized for other purposes, split into multiple tables for different types of information (e.g. one table for event logs and another for user content), etc. The mechanics of how the data is stored are fully encapsulated within the class structure, so users of this system do not need to be aware of the implementation details.
==Files==
==Files==
{{l/ferreteria/code|data/node}}
* {{l/ferreteria/code|data/node}}
* {{l/ferreteria/code|data/node/trunk}}
** {{l/ferreteria/code|data/node/feature.php}} - main API
** {{l/ferreteria/code|data/node/trunk/row.stor.php}}
** {{l/ferreteria/code|data/node/row.stor.php}} - handles all the DB details
** {{l/ferreteria/code|data/node/cards.php}} - not yet used
==Tables==
==Tables==
* {{l/version|sql|node}}: core pseudorecord
* {{l/ver/sql|node}}: the only table
* {{l/version|sql|node_leaf}}: field within a pseudorecord

Latest revision as of 21:18, 12 December 2022

versions: 0.41, 0.42, 0.5

About

The nodes subsystem stores arbitrary hierarchical data within a standard relational database.

The current proof-of-concept implementation stores all data using only one table, but this can easily be optimized for other purposes, split into multiple tables for different types of information (e.g. one table for event logs and another for user content), etc. The mechanics of how the data is stored are fully encapsulated within the class structure, so users of this system do not need to be aware of the implementation details.

Files

Tables

  • node: the only table