Abstract
This class provides meta-information about database objects, such as tables, columns, and indexes.
While the preferred method of database object creation and
deletion is through the MySQL Server,
NdbDictionary also permits the developer to
perform these tasks through the NDB API.
Parent class. None
Child classes.
Dictionary,
Column,
Object
Description. This is a data dictionary class that supports enquiries about tables, columns, and indexes. It also provides ways to define these database objects and to remove them. Both sorts of functionality are supplied using inner classes that model these objects. These include the following inner classes:
Tablefor working with tablesColumnfor creating table columnsIndexfor working with secondary indexesDictionaryfor creating database objects and making schema enquiriesEventfor working with events in the cluster.
Additional Object subclasses model
the tablespaces, logfile groups, datafiles, and undofiles required
for working with MySQL Cluster Disk Data tables (introduced in MySQL
5.1).
Tables and indexes created using NdbDictionary
cannot be viewed from the MySQL Server.
Dropping indexes through the NDB API that were created originally from a MySQL Cluster causes inconsistencies. It is possible that a table from which one or more indexes have been dropped using the NDB API will no longer be usable by MySQL following such operations. In this event, the table must be dropped, and then re-created using MySQL to make it accessible to MySQL once more.
Methods.
NdbDictionary itself has no public methods. All
work is accomplished by accessing its subclasses and their public
members.
NdbDictionary Subclass Hierarchy.
This diagram shows the hierarchy made up of the
NdbDictionary class, its subclasses, and their
enumerated data types:
For the numeric equivalents to enumerations of
NdbDictionary subclasses, see the file
/storage/ndb/include/ndbapi/NdbDictionary.hpp
in the MySQL Cluster source tree.
