Scripts
A script is a text file containing commands in the same form as used by Browse. Use the browse command run fileName to execute a script. Browse then passes the script to the COODBMS server which executes it as a single transaction. If there is an error while the script is being executed, the transaction aborts and the database is restored to the state it had prior to executing the script.
Scripts can also be run using the runScript databaseName branchName fileName utility. This could be handy when maintaining multiple branches under the same server.
The following commands can be used in a script file:
- addKeyword keyword
- addLink [key] pathname
- addOrderedSection [key]
- addSortedSection [key]
- adoptChild [childName] childPathname
- adoptFork [childName] rolonPathname
- backlinkCSecs
- bind fileName
- changeChildName oldName newName
- changeKey oldKey newKey
- children
- createAccount userName
- createChild key
- createWellknown wellknownName
- cu
- du
- elements
- go pathname
- home
- importBinary [key] fileName
- importText [key] fileName
- journal dateTime
- ju
- keywordMatches
- linkCSecs
- lu
- moveAfter what where
- moveBefore what where
- moveFirst what
- moveLast what
- moveParentAfter parent where
- moveParentBefore parent where
- moveParentFirst parent
- moveParentLast parent
- parents
- rbacklinks [csecName]
- remove key
- removeChild key
- removeWellknownName
- resetAccessControlCache
- rlinks [csecName]
- rtree
- setAttribute attName [attValue]
- setHeadline a brief description
- setUpdateGroup [userGroupName]
- setUpdateUser [userName]
- setWellknownName wellknownName
- show
- snapshots
- tree
- up
- wellknown
- wellknownFork wellknownName
- when dateTime
Script Files Included in the COODBMS Zip File
Script files have been included in the download in the client directory: secureMaster.txt and secureBranch.txt. These are covered below.
Securing the Master Database
Two things can be done to secure the master database: (1) block the use of the createMyMasterAccount command by a guest and (2) block queries by guests. This can be done by the browser command run secureMaster.txt, which executes the following sequence of commands:
go /OPERATION_GROUPS/GuestOperations
removeChild createMyMasterAccount
go /USER_GROUPS/GuestGroup/CU/OperationGroups
remove #2
Securing Branches in Other Databases
Three things can be done to secure branches in other databases: (1) block the use of the CreateMyAccount by known guests, (2) block queries by guests and (3) block queries by known users. This can be done by the browser command run secureBranch.txt, which executes the following sequence of comands:
go /OPERATION_GROUPS/KnownGuestOperations
removeChild createMyAccount
go /USER_GROUPS/GuestGroup/CU/OperationGroups
remove #2
go /USER_GROUPS/KnownGuestGroup/CU/OperationGroups
remove #3
