Ferreteria/v0.3/class: Difference between revisions

From Woozle Writes Code
Jump to navigation Jump to search
(list of traits is redundant when we have automated list of all classlike entities)
No edit summary
Line 3: Line 3:
==Data==
==Data==
===Root Classes===
===Root Classes===
* {{l/ferreteria/class|cIOSource}}
* {{l/ferreteria/class|cIOSource}} (TODO: rename to cDataSource)
* {{l/ferreteria/class|cFieldRow}}
* {{l/ferreteria/class|cFieldRow}}
* {{l/ferreteria/class|cPortalRow}}
* {{l/ferreteria/class|cPortalRow}}
===Notes===
===Notes===
Things in need of re-examination:
* interface ifSingleKeyedRow
* Standard storage-PortalRow class expects the Table to have the table name (via {{l/ferreteria/class|tTableSource}}, but other constructions are possible.
''rearrangement in progress''
''rearrangement in progress''



Revision as of 21:45, 7 January 2019

Lists

Data

Root Classes

Notes

Things in need of re-examination:

  • interface ifSingleKeyedRow
  • Standard storage-PortalRow class expects the Table to have the table name (via Template:L/ferreteria/class, but other constructions are possible.

rearrangement in progress

Core functionality:

Database sources:

  • manage what's in the source (selected, sequential access)

Currently, Table (Source) objects define:

There are two types of accessible data, when dealing with databases:

  • data that has been loaded into a black-box "resource" rowset, and can be accessed sequentially
  • data that is being stored in memory, and can be accessed by index (core functionality)