Ferreteria/v0.5/data: Difference between revisions

From Woozle Writes Code
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
=Data Storage Classes=
=Data Storage Classes=
v0.5 includes a [[2021/11/08/data objects refactoring|significant refactoring of how database-related objects are managed]]. The goal was to simplify access to global singleton objects in general, and databases and tabloids in particular, while retaining flexibility (e.g. for different applications to determine the database in which each table is stored).
v0.5 includes a [[2021/11/08/data objects refactoring|significant refactoring of how database-related objects are managed]]. The goal was to simplify access to global singleton objects in general, and databases and tabloids in particular, while retaining flexibility (e.g. for different applications to determine the database in which each table is stored).
{|
|-
| valign=top |
==Pages==
* {{l/ver|db}}: database classes
** {{l/ver|table}}: database table classes
* {{l/ver|portbank}}: data field I/O management
** {{l/ver|feature}}
| valign=top |
==Subsystems==
==Subsystems==
{|
{|
Line 17: Line 26:
|-
|-
| — {{l/ferreteria/code|data/space}} || [[/space]] || data result packaging
| — {{l/ferreteria/code|data/space}} || [[/space]] || data result packaging
|}
|}
|}

Revision as of 14:01, 28 May 2022

Data Storage Classes

v0.5 includes a significant refactoring of how database-related objects are managed. The goal was to simplify access to global singleton objects in general, and databases and tabloids in particular, while retaining flexibility (e.g. for different applications to determine the database in which each table is stored).

Pages

Subsystems

code docs description
data data root folder for data storage classes
data/db db relational database classes
data/fields I/O translation (PortBank) and Features
data/log event log (uses node)
data/node node hierarchical data storage
data/space /space data result packaging