2026/09/03
< 2026
|
Thursday, September 3, 2026 (#246)
|
|
References |
Main Work
a careful re-think of how Ferreteria connection-sessions are structured
Continuing yesterday's re-thinking of how to send a simple SQL command:
Sys\Data\Engine\endpt\Clientasks$this->OEnginefor the Main[1] Command (which opens the Engine for SQL) via$oEng->OServer->OMainCommand.- The Engine creates a Session object from the Command object.
- Note: the Engine has the Connection object ($OCmdConn), and the Command has the Engine object -- so the Session will ask the Command for the Connection to use.
- I decided to put the Connection (now called "$ORunner") in the root Command clade -- starting as a property which can be ignored if we're just using the Connection to build a command-spec. (It only comes into play if we want the Command-object to know how to run the command.)
- Note: the Engine has the Connection object ($OCmdConn), and the Command has the Engine object -- so the Session will ask the Command for the Connection to use.
- working here