The ARCHIVE Storage Engine Feature Support Clustered indexes No Compressed data Yes Data caches No Encrypted data Yes (Implemented in the server via encryption functions.) Foreign key support No Full-text search indexes No Geospatial data type support Yes Geospatial indexing support No Hash indexes No Index caches No Locking granularity Row MVCC No Replication support  (Implemented in the server, rather than in the storage engine.) Yes Storage limits None T-tree indexes No Transactions No Update statistics for data dictionary Yes The  ARCHIVE  storage engine does not support partitioning. 3417 The  ARCHIVE  engine ignores  BLOB  columns if they are not requested and scans past them while reading. ARCHIVE  does not support inserting a value into an  AUTO_INCREMENT  column less than the current maximum column value. Attempts to do so result in an  ER_DUP_KEY  error. The  ARCHIVE  engine supports the  AUTO_INCREMENT  column attribute. The  AUTO_INCREMENT  column can have either a unique or nonunique index. Attempting to create an index on any other column results in an error. The  ARCHIVE  engine also supports the  AUTO_INCREMENT  table option in  CREATE TABLE statements to specify the initial sequence value for a new table or reset the sequence value for an existing table, respectively. The  ARCHIVE  engine supports  INSERT ,  REPLACE , and  SELECT , but not  DELETE  or  UPDATE . It does support  ORDER BY  operations,  BLOB  columns, and spatial data types (see Section 11.4.1, “Spatial Data Types” ). Geographic spatial reference systems are not supported. The  ARCHIVE  engine uses row-level locking. When you create an  ARCHIVE  table, the storage engine creates files with names that begin with the table name. The data file has an extension of  .ARZ . An  .ARN  file may appear during optimization operations. You can check whether the  ARCHIVE  storage engine is available with the  SHOW ENGINES  statement. To examine the source for the  ARCHIVE  engine, look in the  storage/archive  directory of a MySQL source distribution. The  ARCHIVE  storage engine is included in MySQL binary distributions. To enable this storage engine if you build MySQL from source, invoke  CMake  with the  -DWITH_ARCHIVE_STORAGE_ENGINE  option.