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
(moved notes to new "notes" section)
(updates)
Line 37: Line 37:
 
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/ferreteria/class|cIOSource}})
* name of database table ({{l/ferreteria/class|cIOSource_standard_table}}) or other SQL to access it ({{l/ferreteria/class|tSelectable_Source}})
+
* name of database table or other SQL to access it ({{l/ferreteria/class|tQueryableSource}})
** tSelectable_Source might be replaced by '''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 11:32, 7 January 2019

Lists

Data

Root Classes

Traits

Notes

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)