Ferreteria/v2/usage/db/v1: Difference between revisions

From Woozle Writes Code
< Ferreteria‎ | v2‎ | usage‎ | db
Jump to navigation Jump to search
m (Woozle moved page Ferreteria/pieces/db/v1 to Ferreteria/usage/db/v1: this should be a usage guide)
m (Woozle moved page Ferreteria/usage/db/v1 to Ferreteria/v2/usage/db/v1 without leaving a redirect: this is all v2 documentation)
(No difference)

Revision as of 14:38, 19 January 2019

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

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
  • clsDataResult (abs: Template:Ferreteria/code)
    • clsDataResult_MySQL (extends clsDataResult): MySQL data result

helpers