How to Find Joomla Schema Versions in #__schemas

Joomla uses #__schemas to track the last SQL schema-update version processed for extensions that participate in Joomla's schema-update mechanism. To read that state safely, identify the extension on this site, translate #__ to the real database prefix, and use a read-only query before considering any repair.

Identify the extension and database first

  1. Confirm the Joomla database name and table prefix from configuration.php.
  2. Find the extension in the site's prefixed extensions table or Joomla's installed-extensions view.
  3. Record its extension_id, type, element, and installed version.

Extension IDs are installation-specific. Never copy an ID from another Joomla site, documentation example, or old unrelated backup.

Query #__schemas without changing it

Replace the example prefix and extension ID with values from the site:

SELECT extension_id, version_id
FROM `yourprefix_schemas`
WHERE extension_id = 123;

If the query returns a row, version_id is Joomla's recorded SQL schema version for that extension. If no row is returned, record that result rather than inserting one immediately; an absent record is not enough by itself to prove corruption.

Compare the stored version with the extension package

  1. Open the exact installed extension manifest.
  2. Find its declared schema/update path for the site's database driver.
  3. List the numbered SQL update files supplied by that exact package.
  4. Compare those filenames with the stored version_id and the actual database structure.

Joomla processes extension SQL update files in version order and records the last processed schema version. The package and database together are the evidence for what should have run.

Do not confuse schema version with extension version

The extension's manifest version and its SQL schema version are separate values. The manifest-derived version is associated with the extension record, while #__schemas.version_id tracks SQL migration progress. Developers often use similar numbers, but Joomla does not make them interchangeable.

Interpret mismatches safely

A schema version behind the available update files can indicate pending or failed migrations, but it does not prove that manually running the next SQL file is safe. Installer scripts can perform PHP-side migration work in addition to SQL. Likewise, raising version_id without applying required migrations can cause Joomla to skip database changes later.

Before any repair, create a current database backup and prefer Joomla's installer or the extension developer's supported repair/reinstall path.

Verify the result after a repair

Re-run the read-only query, confirm the stored schema version represents migrations that actually completed, and verify the expected tables, columns, indexes, and extension behavior. Keep the backup until both Administrator and frontend functions affected by the extension have been tested.


Need More Help with Joomla?

Still having trouble? Open a support ticket with QuantaCade Support and we'll be happy to help where we can.

Support priority is given to QuantaCade products, services, and customers. However, we're also happy to assist fellow Joomla users with general Joomla questions and troubleshooting when possible.

QuantaCade is an independent Joomla extension developer and is not official Joomla support. Some issues involving third-party extensions, hosting environments, server configurations, or other systems outside our development control may be beyond what we're able to resolve.

Open a Support Ticket