Difference between revisions of "Ferreteria/v0.3/class"

from HTYP, the free directory anyone can edit if they can prove to me that they're not a spambot
Jump to navigation Jump to search
m (Woozle moved page Ferreteria/class to Ferreteria/v3/class without leaving a redirect: this is all v3 documentation, and we still need v2)
(updated template calls)
Line 3: Line 3:
 
==Data==
 
==Data==
 
===Root Classes===
 
===Root Classes===
* {{l/ferreteria/class|cIOSource}} (TODO: rename to cDataSource)
+
* {{l/version|class|cIOSource}} (TODO: rename to cDataSource)
* {{l/ferreteria/class|cFieldRow}}
+
* {{l/version|class|cFieldRow}}
* {{l/ferreteria/class|cPortalRow}}
+
* {{l/version|class|cPortalRow}}
 
===Notes===
 
===Notes===
 
Things in need of re-examination:
 
Things in need of re-examination:
Line 15: Line 15:
  
 
Core functionality:
 
Core functionality:
* handle current row - {{l/ferreteria/class|cFieldRow}}
+
* handle current row - {{l/version|class|cFieldRow}}
 
* handle multiple rows
 
* handle multiple rows
** sequential - {{l/ferreteria/class|tSequentialAccess}}
+
** sequential - {{l/version|class|tSequentialAccess}}
 
*** status (how many rows found)
 
*** status (how many rows found)
 
*** position row cursor
 
*** position row cursor
Line 28: Line 28:
  
 
Currently, Table (Source) objects define:
 
Currently, Table (Source) objects define:
* name of single-row class ({{l/ferreteria/class|cIOSource}})
+
* name of single-row class ({{l/version|class|cIOSource}})
* name of database table or other SQL to access it ({{l/ferreteria/class|tQueryableSource}})
+
* name of database table or other SQL to access it ({{l/version|class|tQueryableSource}})
  
 
There are two types of accessible data, when dealing with databases:
 
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 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)
 
* data that is being stored in memory, and can be accessed by index (core functionality)

Revision as of 15:42, 19 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 tTableSource, but other constructions are possible.

rearrangement in progress

Core functionality:

  • handle current row - cFieldRow
  • handle multiple rows
    • sequential - tSequentialAccess
      • status (how many rows found)
      • position row cursor
      • access current row
      • end-of-rowset flag
    • indexed

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)