MyISAM storage engine
E100301
The MyISAM storage engine is a legacy MySQL table format known for fast read performance, simple design, and lack of transactional and foreign key support.
All labels observed (2)
| Label | Occurrences |
|---|---|
| MyISAM | 2 |
| MyISAM storage engine canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T816901 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MyISAM storage engine Context triple: [MySQL, supportsFeature, MyISAM storage engine]
-
A.
InnoDB storage engine
InnoDB storage engine is a widely used transactional storage engine for MySQL that provides ACID compliance, row-level locking, and crash recovery for reliable, high-performance database operations.
-
B.
MariaDB
MariaDB is an open-source relational database management system, forked from MySQL, known for its compatibility, performance, and community-driven development.
-
C.
MySQL
MySQL is a widely used open-source relational database management system known for its reliability, performance, and role in powering many web applications and services.
-
D.
MySQL HeatWave
MySQL HeatWave is a fully managed, in-memory query acceleration and analytics engine integrated with MySQL to deliver high-performance OLTP and OLAP processing on the same database service.
-
E.
B-tree
A B-tree is a self-balancing tree data structure that maintains sorted data and allows efficient insertion, deletion, and search operations, commonly used to implement database indexes.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: MyISAM storage engine Target entity description: The MyISAM storage engine is a legacy MySQL table format known for fast read performance, simple design, and lack of transactional and foreign key support.
-
A.
InnoDB storage engine
InnoDB storage engine is a widely used transactional storage engine for MySQL that provides ACID compliance, row-level locking, and crash recovery for reliable, high-performance database operations.
-
B.
MariaDB
MariaDB is an open-source relational database management system, forked from MySQL, known for its compatibility, performance, and community-driven development.
-
C.
MySQL
MySQL is a widely used open-source relational database management system known for its reliability, performance, and role in powering many web applications and services.
-
D.
MySQL HeatWave
MySQL HeatWave is a fully managed, in-memory query acceleration and analytics engine integrated with MySQL to deliver high-performance OLTP and OLAP processing on the same database service.
-
E.
B-tree
A B-tree is a self-balancing tree data structure that maintains sorted data and allows efficient insertion, deletion, and search operations, commonly used to implement database indexes.
- F. None of above. chosen
Statements (49)
| Predicate | Object |
|---|---|
| instanceOf |
MySQL storage engine
ⓘ
database storage engine ⓘ |
| characteristic |
no MVCC
ⓘ
no foreign key enforcement ⓘ non-transactional ⓘ |
| crashRecovery | non-automatic ⓘ |
| defaultStorageEngineFrom |
MySQL
ⓘ
surface form:
MySQL 3.23
|
| defaultStorageEngineUntil |
MySQL
ⓘ
surface form:
MySQL 5.5
|
| developedBy | MySQL AB ⓘ |
| developedFor |
MySQL
ⓘ
surface form:
MySQL relational database management system
|
| doesNotSupport |
ACID compliance
ⓘ
foreign keys ⓘ referential integrity constraints ⓘ row-level locking ⓘ transactions ⓘ |
| filePerTable | true ⓘ |
| introducedIn |
MySQL
ⓘ
surface form:
MySQL 3.23
|
| knownFor |
fast read performance
ⓘ
simple design ⓘ |
| lockingGranularity | table ⓘ |
| maintainedBy | Oracle Corporation ⓘ |
| metadataStoredIn | .frm files ⓘ |
| notRecommendedFor |
high-concurrency write workloads
ⓘ
transactional applications ⓘ |
| optimizedFor | read-heavy workloads ⓘ |
| predecessorOf | Aria storage engine ⓘ |
| recommendedAlternative | InnoDB storage engine ⓘ |
| replacedBy | InnoDB storage engine ⓘ |
| status | legacy ⓘ |
| storesDataIn | .MYD files ⓘ |
| storesIndexesIn | .MYI files ⓘ |
| supports |
AUTO_INCREMENT columns
ⓘ
FULLTEXT indexes before InnoDB ⓘ compressed tables ⓘ concurrent inserts under certain conditions ⓘ delayed inserts ⓘ dynamic row format ⓘ fixed-length rows ⓘ full-text indexing ⓘ index prefix compression ⓘ myisamchk utility ⓘ spatial indexes ⓘ static row format ⓘ table-level locking ⓘ table-level repair ⓘ variable-length rows ⓘ |
| usedFor | read-only or read-mostly tables ⓘ |
| usedIn | older MySQL installations ⓘ |
| vulnerableTo | table corruption after crashes ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: MyISAM storage engine Description of subject: The MyISAM storage engine is a legacy MySQL table format known for fast read performance, simple design, and lack of transactional and foreign key support.
Referenced by (3)
Full triples — surface form annotated when it differs from this entity's canonical label.
this entity surface form:
MyISAM
this entity surface form:
MyISAM