Identifier for this object’s parent object; the same as the dict_obj_info  table’s id  column 

• parent_name 

Fully qualified name of this object’s parent object; the same as the dict_obj_info  table’s fq_name column 

For a table, this has the form database_name /def/ table_name . For an index, the name is sys/ def/ table_id / index_name . For a primary key, it is sys/def/ table_id /PRIMARY , and for a unique key it is sys/def/ table_id / uk_name $unique 

• root_type 

The DICT  object type of the root object; join on dict_obj_types  to obtain the name of the object type 

• root_id 

Identifier for the root object; the same as the dict_obj_info  table’s id  column 

• root_name 

Fully qualified name of the root object; the same as the dict_obj_info  table’s fq_name  column 

• level 

Level of the object in the hierarchy 

• path 

Complete path to the object in the NDB  object hierarchy; objects are separated by a right arrow (represented as -> ), starting with the root object on the left 

• indented_name 

The name  prefixed with a right arrow (represented as -> ) with a number of spaces preceding it that correspond to the object’s depth in the hierarchy 

The path  column is useful for obtaining a complete path to a given NDB  database object in a single line, whereas the indented_name  column can be used to obtain a tree-like layout of complete hierarchy information for a desired object. 

Example : Assuming the existence of a test  database and no existing table named t1  in this database, execute the following SQL statement: 

CREATE TABLE test.t1 ( a INT PRIMARY KEY, b INT, UNIQUE KEY(b) ) ENGINE = NDB; 

You can obtain the path to the table just created using the query shown here: 

mysql> SELECT path FROM ndbinfo.dict_obj_tree -> WHERE name LIKE ’test%t1’; +-------------+ | path | +-------------+ | test/def/t1 | +-------------+ 

