Ferreteria/v0.6/code/sys/Requests: Difference between revisions
< Ferreteria | v0.6
Jump to navigation
Jump to search
(Created page with "{{fmt/title|Request subsystems}} There are (currently) the following types of request: * Requests to a database engine: ** {{fmt/clade|Woozalia\Ferret\Sys\Data\reqs\Engine|AdminRq}} is for administration operations: backup, restore, user management, etc. ** {{fmt/clade|Woozalia\Ferret\Sys\Data\reqs\Engine|CommRq}} is for data (should probably be renamed) * Input requests: ** {{fmt/clade|Woozalia\Ferret\Sys\Events|InputReq}} The purpose of engine requests is to allow con...") |
No edit summary |
||
| Line 8: | Line 8: | ||
The purpose of engine requests is to allow consolidation of all the pieces needed to perform operations ''without'' knowing what engine or connection they will be used on. | The purpose of engine requests is to allow consolidation of all the pieces needed to perform operations ''without'' knowing what engine or connection they will be used on. | ||
==Sequence of Events== | |||
* <code>{{fmt/clade|Woozalia\Ferret\Sys\Data|DbConn}}->DoAdminRequest()</code> calls <code>AdminRq->AskEngine()</code> with itself as the argument. | |||
* <code>AdminRq->AskEngine()</code> does any necessary calculations, then calls the appropriate Engine object or sub-object (e.g. Schema) to do the operation. | |||
Revision as of 01:51, 11 March 2025
|
Request subsystems
|
There are (currently) the following types of request:
- Requests to a database engine:
- Input requests:
The purpose of engine requests is to allow consolidation of all the pieces needed to perform operations without knowing what engine or connection they will be used on.
Sequence of Events
DbConn->DoAdminRequest()callsAdminRq->AskEngine()with itself as the argument.AdminRq->AskEngine()does any necessary calculations, then calls the appropriate Engine object or sub-object (e.g. Schema) to do the operation.