Difference between revisions of "Ferreteria/v0.3/class"
< Ferreteria | v0.3
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 | + | * name of database table or other SQL to access it ({{l/ferreteria/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 11:32, 7 January 2019
Lists
Data
Root Classes
Traits
- tDataDesign
- tDataDesign_singleKey
tFieldClasses- tInternalStorage
- tLoadableRow
- tQueryableSource
tSelectable_Source- tSequentialAccess
- tSimpleFields
tSource_SingleKeyed- tSourcedStorage
- tTableSource
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
- sequential - tSequentialAccess
Database sources:
- manage what's in the source (selected, sequential access)
Currently, Table (Source) objects define:
- name of single-row class (cIOSource)
- name of database table or other SQL to access it (tQueryableSource)
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)