NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Packagist · #1885 most downloaded on Packagist
Doctrine Extensions for MySQL and PostgreSQL.
Last release 28 days ago
10 Sep 2026
Release timing varies
gaps range from 1 weeks to 1.6 years
Rarely documented
notes for 8 of 41 stable releases
Nothing withdrawn
no release was ever pulled
12 years old
41 releases · first in 2014
Restricts the target type of the CAST DQL function to the supported type names and to a numeric length or precision, so a query expression can no long
Restricts the target type of the CAST DQL function to the supported type names and to a numeric
length or precision, so a query expression can no longer place arbitrary text into the type position
of the generated SQL.
What is changed
CAST expression is accepted only when its target type is one of the documented type names. A name that merely begins with a supported one, such as timestamp or int8, is now rejected as unsupported.CAST(expr as char(5)) and CAST(expr as decimal(10, 2)) keep working and any other content is reported as a syntax error.jsonb is a supported type name in its own right, so a cast to it is accepted and renders as it did before.CAST(expr as string(12)) produces varchar(12) on PostgreSQL and char(12) on MySQL instead of being passed through unchanged.Impact
timestamp, timestamptz, int8) now get a syntax error and have to use one of the supported type names.doctrine/orm 2.8 with doctrine/lexer 1 and doctrine/dbal 2.12, which is the combination OroPlatform 4.2 is fixed to.One column per quarter.
Restricts the target type of the CAST DQL function to the supported type names and to a numeric length or precision, so a query expression can no long
Restricts the target type of the CAST DQL function to the supported type names and to a numeric
length or precision, so a query expression can no longer place arbitrary text into the type position
of the generated SQL.
What is changed
CAST expression is accepted only when its target type is one of the documented type names. A name that merely begins with a supported one, such as timestamp or int8, is now rejected as unsupported.CAST(expr as char(5)) and CAST(expr as decimal(10, 2)) keep working and any other content is reported as a syntax error.jsonb is a supported type name in its own right, so a cast to it is accepted and renders as it did before.CAST(expr as string(12)) produces varchar(12) on PostgreSQL and char(12) on MySQL instead of being passed through unchanged.Impact
timestamp, timestamptz, int8) now get a syntax error and have to use one of the supported type names.doctrine/orm 2.8 with doctrine/lexer 1 and doctrine/dbal 2.12, which is the combination OroPlatform 4.2 is fixed to.add github ci PR #100 2.x by @x86demon in #102
Full Changelog: 2.0.4...2.0.5
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Fix MariaDB compatibility with DBAL 4 by @tups in #115
Compatibility with Doctrine ORM 3.0 minimum by @monpetitplacement and @Gwemox in #99
Full Changelog: 3.0-alpha3...3.0-alpha4
Set requirement for doctrine/lexer by @alexander-schranz in #96
Full Changelog: 3.0-alpha2...3.0-alpha3
Nothing published for this version
Nothing published for this version
Release 3.0 - Doctrine ORM 3 Support
This major release brings full compatibility with Doctrine ORM 3.0, representing a significant modernization of the library to support the latest PHP and Doctrine ecosystem standards.
The following method signatures have been updated. If you have created custom functions by extending library classes, you may need to update your code:
FunctionFactory::create(string $platformName, string $functionName, array $parameters): PlatformFunctionNodeCast#checkType($type) has been replaced with isSupportedType(string $type): boolTimestampDiff#checkUnit($unit) has been replaced with isSupportedUnit(string $unit): boolAbstractTimestampAwarePlatformFunctionNode#getTimestampValue($expression, SqlWalker $sqlWalker): stringIf you only registered the functions and types provided by this library with Doctrine, most likely you do not need to make any changes to your code. Simply update your composer.json:
{
"require": {
"oro/doctrine-extensions": "^3.0"
}
}This release was made possible by the Oro team and community contributors who worked to ensure compatibility with Doctrine ORM 3.0. Special thanks to all who tested the alpha and beta releases.
If you encounter any issues with this release, please report them on our GitHub Issues page.
Full Changelog: 2.0.5...3.0
In this release will be introduced compatibility with latest versions of Doctrine
Moved to latest PHPUnit
Restricts the target type of the CAST DQL function to the supported type names and to a numeric length or precision, so a query expression can no long
Restricts the target type of the CAST DQL function to the supported type names and to a numeric
length or precision, so a query expression can no longer place arbitrary text into the type position
of the generated SQL.
What is changed
CAST expression is accepted only when its target type is one of the documented type names. A name that merely begins with a supported one, such as timestamp or int8, is now rejected as unsupported.CAST(expr as char(5)) and CAST(expr as decimal(10, 2)) keep working and any other content is reported as a syntax error.jsonb is a supported type name in its own right, so a cast to it is accepted and renders as it did before.CAST(expr as string(12)) produces varchar(12) on PostgreSQL and char(12) on MySQL instead of being passed through unchanged.Impact
timestamp, timestamptz, int8) now get a syntax error and have to use one of the supported type names.doctrine/orm 2.8 with doctrine/lexer 1 and doctrine/dbal 2.12, which is the combination OroPlatform 4.2 is fixed to.Your coding agent can read these notes before it upgrades. Set up the MCP server →