Viewing Super-databases and Sub-databases
You can call the GET:/manage/v2/databases/{id|name}/super-databases resource address to return a list of the super-databases associated with a sub-database. For example, to view the super-databases of the subdb1 database, do the following:
$ curl --anyauth --user user:password -X GET \ -H 'Content-type: application/xml' \ http://MyHost:8002/manage/v2/databases/subdb1/super-databases
You can call the GET:/manage/v2/databases/{id|name}/sub-databases resource address to return a list of the sub-databases associated with a super-database. For example, to view the sub-databases of the superdb1 database, do the following:
$ curl --anyauth --user user:password -X GET \ -H 'Content-type: application/xml' \ http://MyHost:8002/manage/v2/databases/superdb1/sub-databases
Note
Since updates can happen at both the super-database and the sub-database level, duplicate URIs are more likely in super-databases. Some automatically generated URIs may produce duplicates at the super-database level. This is true not only for automatically-generated URIs for graph documents, but also may be a problem for the bitemporal LSQT documents, and for directory properties fragments created with automatic-directory-creation. Duplicate URIs will generate a DUPURI exception.