Add classes to represent schema information tables #22
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Currently all schema information is directly passed around as associative arrays, leading to constant retesting on a live MariaDB instance what the possible values are. The MariaDB document does not always provide all possible values either.
A fully type-hinted class should be declared for each table in the information schema. Use lazy ghost objects to create partial instances.