Talk:DB Variables Configuration
Following section to with new para to replace current text
Setting db variables to default values
Any db variable that has a default value can be reset to the default by deleting the variable entirely, then re-initializing the default database values as follows:
config delprop <key> <prop> /etc/e-smith/events/actions/initialize-default-databases
Delete a property value
To delete the property
db accounts delprop <key> <prop>
Reset a property value
To reset to an empty value
db accounts setprop <key> <prop> ''
Angle brackets around the key and prop markers.
Split delete and reset.
English corrections.
Questions:
Does initialize-default-databases only set the defaults on poperties that are missing? If so I think that needs to be stated, I'd not want to set the entire db to defaults...
Yes, my reading is that it just returns defaults on those missing.
That is my reading as well but want to be absolutely sure. B-)
Allsorts (talk) 13:54, 14 February 2013 (MST)
The angle brackets is how I always indicate that something is a marker rather than what you actually type. What is the contribs.org style?
Cool, do it..
"config ..." or "db accounts ...", let's be consistent please. "db accounts ..." would only work if the <key> <prop> is in the accounts db wouldn't it? "config ..." works across all the db's doesn't it?
Allsorts (talk) 19:02, 13 February 2013 (MST)
The first command syntax is original text, what are you suggesting, change it or change the others Terry Fage (talk) 19:10, 13 February 2013 (MST)
Change the "db accounts" to "config" if the config version is the one that works across all db's, which I think it is.
Allsorts (talk) 13:54, 14 February 2013 (MST)
Not sure about leaving out a command that works and is not just an old hanger on from a past release. Does it hurt? Can it cause confusion, don't think so.. Terry Fage (talk) 04:22, 15 February 2013 (MST)
Posed the question in the list Terry Fage (talk) 04:34, 15 February 2013 (MST)
