2026/03/11

Wednesday, March 11, 2026 (#70)

Tuesday Wednesday Thursday posts: prev < this > next

References Ferreteria/v0.6/clade/Sys/Data/aux/MetaPair ‎ (← links) Futilities/v0.6/clade/Sys/dba/InReq/@removed ‎ (← links) 2026/03/10 ‎ (← links) Ferreteria/v0.6/clade/Sys/Data/Engine/aux/ActionRq/Admin/ListSchemas/@removed ‎ (← links) Ferreteria/v0.6/clade/Sys/Data/Engine/aux/ActionRq/Admin/ListSchemas ‎ (← links) 2026/03/12 ‎ (← links)

09:12

Actions:

• 🟢 created basic page for ListSchemas
• 🟡 finish revisions for ImportSchema

10:18

• Command: ./go schema:htyp_mw replace:1 -i:local
  • Result: errors out at $oCanals->ConveyCheck() because no Canal objects have been added -- presumably because the caller didn't add any streams to $oCmd.

...when there should be at least one: the SQL data file, as an input stream.

12:41

• Q1: What does PairCheck() actually do?
  • A1:
    • verifies that the folder exists
    • reads folder's file-listing
    • gets list of .json files found
    • converts it to a list of base-names
    • gets list of .sql files found
    • for each .sql file:
      • create a MetaPair object and provision its "data" side with details from said file
      • attempt to also provision its "info" side with details from eponymous .json file (if not found, fill in minimal details to create the file)
• Q2: What is its relationship to MetaPair?
  • A2: PairCheck is about creating a list of MetaPair objects from the contents of a folder.
    • Perhaps this could be a static function of MetaPair instead of requiring a Fo (folder-node) descendant (Sys\dba\files\DataFolder) -- or perhaps DataFolder belongs as a Ferreteria Engine auxiliary clade instead of being DBA-specific, since MetaPair already is there.

20:36

Re A2: I decided to do the easier thing, for now, and just move DataFolder up to Ferreteria -- or, actually, move Futil's Sys\dba\files folder there:

• [WFu]Sys\dba\files\DataFiles ⇒ [WFe]Sys\Data\aux\files\DataFiles
• [WFu]Sys\dba\files\DataFolder ⇒ [WFe]Sys\Data\aux\files\DataFolder