This means that if a value cannot be found in the "aFrame" database table, then it will get it from the parent database table.
This allows you to make templates that many tables inherit from. This has many advantages compared to using the defaults
table; You can customise the template using your own config menu to apply changes to all objects that inherit from it, and
all the changes are persistent.
The database framework uses metatables to automatically select and retrieve the appropriate values automatically for you using a three step pattern:
Check if the key/value pair is located in the saved variable table.
If not found, check if the key/value pair is located in the defaults table.
If not found, check if the Observer has a parent. If it does, repeat step 1 using the parent Observer.
You can parse and set database values using path addresses (stringns) to query values from the database:
value = db:ParsePathValue("global.core.settings["..moduleName.."]")
EDIT: Just updated it to support many databases running simultaneously using db:CreateDatabase() method.
The new version requires a different way of setting it up and starting the database. Information is on the download page.