Ferreteria/v0.5/table: Difference between revisions
< Ferreteria | v0.5
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
Tables have been [[wooz:2021/12/17/The Great Data-Class Restacking|greatly simplified]] since v0.4, where they (along with Rows and Rowsets) were the basis for specialized classes that constituted what is now called {{l/ver|Feature}}s. There are now just two classes: | Tables have been [[wooz:2021/12/17/The Great Data-Class Restacking|greatly simplified]] since v0.4, where they (along with Rows and Rowsets) were the basis for specialized classes that constituted what is now called {{l/ver|Feature}}s. There are now just two classes: | ||
* <code>cTabloid</code>: can use (but does not require) a Feature object; also maintains a static Table registry. Does nothing else. | * <code>cTabloid</code>: can use (but does not require) a Feature object; also maintains a static Table registry. Does nothing else. | ||
* <code>cTable</code>: adds functions to | * <code>cTable</code>: adds | ||
** functions to access the Table's SQL name | |||
** function to access the database engine object | |||
** traits for database interaction (see {{l/ferreteria/code|data/db/table/traits.php}}) | |||
It's uncertain whether this is a good design, or if either or both of these classes are even needed. | It's uncertain whether this is a good design, or if either or both of these classes are even needed. | ||
Revision as of 16:42, 15 March 2022
About
- code files: data/db/table
Tables have been greatly simplified since v0.4, where they (along with Rows and Rowsets) were the basis for specialized classes that constituted what is now called Features. There are now just two classes:
cTabloid: can use (but does not require) a Feature object; also maintains a static Table registry. Does nothing else.cTable: adds- functions to access the Table's SQL name
- function to access the database engine object
- traits for database interaction (see data/db/table/traits.php)
It's uncertain whether this is a good design, or if either or both of these classes are even needed.
Related
- Table Spec classes
- The Table Registry involves both Tables and Table Specs.