What data types are supported by MySQL Cluster?
In MySQL 5.1, MySQL Cluster supports all of the usual MySQL data types, except for those associated with MySQL’s spatial extensions. (Spatial data types and spatial indexes are supported only by MyISAM; see Spatial Extensions, for more information.) In addition, there are some differences with regard to indexes when used with NDB tables.
MySQL Cluster supports all of the usual MySQL data types, with the exception of those associated with MySQL’s spatial extensions. (See Chapter 18, Spatial Extensions.) In addition, there are some differences with regard to indexes when used with NDB tables. Note: MySQL Cluster Disk Data tables (that is, tables created with TABLESPACE … STORAGE DISK ENGINE=NDBCLUSTER) have only fixed-width rows. This means that (for example) each Disk Data table record containing a VARCHAR(255) column requires space for 255 characters (as required for the character set and collation being used for the table), regardless of the actual number of characters stored therein. See Section 16.13, “Known Limitations of MySQL Cluster”, for more information about these issues.
MySQL Cluster 5.1, including MySQL CLuster NDB 6.2 and 6.3, supports all of the usual MySQL data types, including those associated with MySQL’s spatial extensions; however, the NDBCLUSTER storage engine does not support spatial indexes. (Spatial indexes are supported only by MyISAM; see Section 11.13, “Spatial Extensions”, for more information.) In addition, there are some differences with regard to indexes when used with NDB tables.
MySQL Cluster supports all of the usual MySQL data types, with the exception of those associated with MySQL’s spatial extensions. (See Chapter 17, Spatial Extensions.) In addition, there are some differences with regard to indexes when used with NDB tables. Note: MySQL Cluster Disk Data tables (that is, tables created with TABLESPACE … STORAGE DISK ENGINE=NDBCLUSTER) have only fixed-width rows. This means that (for example) each Disk Data table record containing a VARCHAR(255) column requires space for 255 characters (as required for the character set and collation being used for the table), regardless of the actual number of characters stored therein. See Section 15.13, “Known Limitations of MySQL Cluster”, for more information about these issues.
MySQL Cluster supports all of the usual MySQL data types, with the exception of those associated with MySQL’s spatial extensions. (See Chapter 17, Spatial Extensions.) In addition, there are some differences with regard to indexes when used with NDB tables. Note: MySQL Cluster Disk Data tables (that is, tables created with TABLESPACE … STORAGE DISK ENGINE=NDBCLUSTER) have only fixed-width rows. This means that (for example) each Disk Data table record containing a VARCHAR(255) column requires space for 255 characters (as required for the character set and collation being used for the table), regardless of the actual number of characters stored therein. See Section 15.13, “Known Limitations of MySQL Cluster”, for more information about these issues.