InnoDB
Storage engine for the MySQL database management system
InnoDB is a storage engine for the database management system MySQL and MariaDB. Since the release of MySQL 5.5.5 in 2010, it replaced MyISAM as MySQL's default table type. It provides the standard ACID-compliant transaction features, along with foreign key support (declarative referential integrity). It is included as standard in most binaries distributed by MySQL AB, the exception being some OEM versions.
Description
InnoDB became a product of Oracle Corporation after its acquisition of the Finland-based company Innobase in October 2005. The software is dual licensed; it is distributed under the GNU General Public License, but can also be licensed to parties wishing to combine InnoDB in proprietary software.
InnoDB supports:
Both SQL and XA transactions
Tablespaces
Foreign keys
Full text search indexes, since MySQL 5.6 (February 2013) and MariaDB 10.0
Spatial operations, following the OpenGIS standard
Virtual columns, in MariaDB
See also
Comparison of MySQL database engines
References
External links
Mysqltutorial.org, InnoDB and other table types in MySQL
The InnoDB Storage Engine, in the MySQL manual.
“InnoDB” enters the record as storage engine for the MySQL database management system. Crown Archives preserves that source wording while asking what InnoDB, Storage and engine can confirm, complicate or overturn.
Why this record matters
“InnoDB” is worth following because a concise public description often conceals a longer documentary argument. Here, InnoDB, Storage and engine provides the most credible route into that argument.
Named sources, stable identifiers and responsible institutions provide the strongest route from overview to verifiable evidence. The source revision retrieved here is dated Jul 22, 2026. The linked authority identifier is Q838388. None of the 1 selected statements returned an explicit reference. The first chronological checks are 2010, 2005 and 2013.
Overview language is designed for orientation and should not be treated as a substitute for the evidence cited beneath it. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “InnoDB”, its source revision and the description used here.
- Expand the search: follow InnoDB primary sources, InnoDB archive and InnoDB research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “InnoDB”?
- Which cited source is closest to the event, object or claim?
- Which institution is responsible for the underlying evidence?
Search terms from this dossier
This entry incorporates text from “InnoDB” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.