Explanation of the "%DEFAULTDB" database in 2016.1.0
During a fine breakfast at Global Summit 2016 I was asked about the %DEFAULTDB database that now appears when creating the %ALL namespace. Until the documentation on "Mapping a Package Across Multiple Namespaces" is updated to include the use of subscript level mapping for all namespaces here is a brief explanation for this change in 2016.1: When creating a global subscript level mapping in the %ALL namespace the database that was used for the non-subscripted global could not be set to be the default database for each namespace. This behavior prevents using %ALL namespace to help manage subscript level mappings that are configured on all namespaces. Now in 2016.1.0 one enters %DEFAULTDB as the destination. For example ^james("doc") mapped to COMMON database and ^james mapped to %DEFAULTDB means data in ^james("doc") will come from the COMMON database when in any namespace but all other ^james data will be stored in the default global database for a namespace. Thanks to John Murray for the question.