---
title: "Breaking: #68401 - SqlParser moved into EXT:dbal"
manual: "TYPO3 Core Changelog"
version: "main"
permalink: "https://docs.typo3.org/permalink/changelog:breaking-68401"
source: "Changelog/7.5/Breaking-68401-SqlParserMovedIntoEXTdbal.rst"
typo3-version: "7.5"
typo3-major: 7
type: "breaking"
issue: 68401
forge: "https://forge.typo3.org/issues/68401"
tags: ["PHP-API", "Database", "ext:dbal"]
rendered: "2026-09-19T12:12:50+00:00"
---

# Breaking: #68401 - SqlParser moved into EXT:dbal {#breaking-68401}

See [forge#68401](https://forge.typo3.org/issues/68401)

## Description {#description}

The SQL Parser included with the core has not been in use by anything
except EXT:dbal for some time. The SQL parser has been merged with the
version in EXT:dbal which now provides parsing and compiling of SQL
statements for MySQL as well as other DBMS.

## Impact {#impact}

There is no impact for the core as EXT:dbal was the sole user of the SQL
parser and it has been migrated into EXT:dbal.

As the parsing and the compiling of SQL statements has been separated into
multiple classes the non-public interface of `SqlParser` has changed.
Classes extending SqlParser need to be adjusted to the new interface.

## Affected Installations {#affected-installations}

Installations with 3rd party extensions that use `TYPO3CMSCoreDatabaseSqlParser`.

## Migration {#migration}

Update the code to use `TYPO3CMSDbalDatabaseSqlParser` instead of
`TYPO3CMSCoreDatabaseSqlParser` or install EXT:compatibility6 which
maps the old class names to the new ones in EXT:dbal.