Ferreteria/v2/usage/db/v1: Difference between revisions
< Ferreteria | v2 | usage | db
Jump to navigation
Jump to search
(extracted from main db page) |
m (Woozle moved page User:Woozle/Ferreteria/pieces/db/v1 to Ferreteria/pieces/db/v1: is finished enough) |
(No difference)
| |
Revision as of 00:17, 27 January 2017
About
The division of duties between the different class-families was rather muddled. When PHP deprecated the default MySQL library, it seemed easier to rewrite the whole structure from the ground up than to try to figure out how to work in support for the MySQLi library.
Files
- Template:Ferreteria/code
- Template:Ferreteria/code
- Template:Ferreteria/code
- Template:Ferreteria/code
- Template:Ferreteria/code
- Template:Ferreteria/code
Classes
database connections & results
- clsDatabase_abstract (abs: Template:Ferreteria/code)
- clsDatabase (extends clsDatabase_abstract): this is actually specific to a particular library for MySQL, so it should probably be renamed
to reflect that.
- clsDataEngine (abs: Template:Ferreteria/code)
- clsDataEngine_CliSrv (abs; extends clsDataEngine): client-server database engine
- clsDataEngine_MySQL (extends clsDataEngine_CliSrv): MySQL database engine using deprecated mysql library
- clsDataEngine_MySQLi (abs; extends clsDataEngine_CliSrv): MySQL database engine using MySQLi library
- clsDataEngine_DBX (abs; extends clsDataEngine_CliSrv): MySQL database engine using dbx library
- clsDataEngine_CliSrv (abs; extends clsDataEngine): client-server database engine
- clsDataResult (abs: Template:Ferreteria/code)
- clsDataResult_MySQL (extends clsDataResult): MySQL data result
helpers
- clsSQLFilt (Template:Ferreteria/code)