files, it also the same as the value shown for the log_id  column in the ndbinfo logbuffers  and logspaces  tables 

• version 

Object version 

• state 

Object state 

• parent_obj_type 

Parent object’s type (a dict_obj_types  type ID); 0 indicates that the object has no parent 

• parent_obj_id 

Parent object ID (such as a base table); 0 indicates that the object has no parent 

• fq_name 

Fully qualified object name; for a table, this has the form database_name /def/ table_name , for a primary key, the form is sys/def/ table_id /PRIMARY , and for a unique key it is sys/ def/ table_id / uk_name $unique 

## 23.5.14.22 The ndbinfo dict_obj_tree Table 

The dict_obj_tree  table provides a tree-based view of table information from the dict_obj_info table. This is intended priarily for use in testing, but can be useful in visualizing hierachies of NDB  database objects. 

The dict_obj_tree  table contains the following columns: 

• type 

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

• id 

Object identifier; same as the id  column in dict_obj_info 

For Disk Data undo log files and data files, this is the same as the value shown in the LOGFILE_GROUP_NUMBER  column of the INFORMATION_SCHEMA.FILES  table; for undo log files, it also the same as the value shown for the log_id  column in the ndbinfo logbuffers  and logspaces tables 

• name 

The fully qualified name of the object; the same as the fq_name  column in dict_obj_info 

For a table, this is database_name /def/ table_name  (the same as its parent_name ); for an index of any type, this takes the form NDB$INDEX_ index_id _CUSTOM 

• parent_type 

The DICT  object type of this object’s parent object; join on dict_obj_types  to obtain the name of the object type 

• parent_id 

