-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[Cache] Split PdoAdapter into DoctrineDbalAdapter #43362
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
GromNaN
commented
Oct 7, 2021
•
edited
Loading
edited
Q | A |
---|---|
Branch? | 5.4 |
Bug fix? | no |
New feature? | yes |
Deprecations? | yes |
Tickets | Fix #42962 |
License | MIT |
Doc PR | symfony/symfony-docs#15903 |
059b705
to
af1fdc3
Compare
114ff31
to
6a587b8
Compare
Tests are green. |
if (!class_exists(DoctrineSchemaConfiguratorInterface::class)) { | ||
$this->markTestSkipped('This test requires symfony/cache >=5.4'); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You've bumped the doctrine/cache
dependency to 5.4, so this block should not be needed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removed this check, but the test will fail till the PR get merged into 5.4
Symfony\Bridge\Doctrine\Tests\SchemaListener\DoctrineDbalCacheAdapterSchemaSubscriberTest::testPostGenerateSchema
PHPUnit\Framework\MockObject\UnknownTypeException: Class or interface "Symfony\Component\Cache\Adapter\DoctrineSchemaConfiguratorInterface" does not exist
src/Symfony/Component/Cache/Adapter/DoctrineSchemaConfiguratorInterface.php
Show resolved
Hide resolved
4c1a11a
to
f0775df
Compare
43fea94
to
cab6dca
Compare
2653ea9
to
a44a730
Compare
a44a730
to
db665be
Compare
Thank you @GromNaN. |
Would be great if someone changed this in DoctrineBundle. I think that currently this functionality is silently broken with Symfony 6, because in bundle we use class_exists checks for deprecated class that was removed from Symfony 6. This is why I didn't make it easy for symfony folks to declare symfony 6 compatibility btw. This change came after we declared compatibility with Symfony 6 and now constraints are wrong because this is most likely broken. edit: Ah looks like work is ongoing here already doctrine/DoctrineBundle#1417 |
…s (andrew-demb) This PR was merged into the 5.4 branch. Discussion ---------- DoctrineDbalAdapter: Fix deprecation message placeholders | Q | A | ------------- | --- | Branch? | 5.4 | Bug fix? | no | New feature? | no <!-- please update src/**/CHANGELOG.md files --> | Deprecations? | no <!-- please update UPGRADE-*.md and src/**/CHANGELOG.md files --> | Tickets | - <!-- prefix each issue number with "Fix #", no need to create an issue if none exist, explain below instead --> | License | MIT | Doc PR | -. <!-- required for new features --> <!-- Replace this notice by a short README for your feature/bugfix. This will help people understand your PR and can be used as a start for the documentation. Additionally (see https://symfony.com/releases): - Always add tests and ensure they pass. - Never break backward compatibility (see https://symfony.com/bc). - Bug fixes must be submitted against the lowest maintained branch where they apply (lowest branches are regularly merged to upper ones so they get the fixes too.) - Features and deprecations must be submitted against branch 5.x. - Changelog entry should follow https://symfony.com/doc/current/contributing/code/conventions.html#writing-a-changelog-entry --> Deprecation introduced in #43362 has a typo in interpolation - wrong parameter order Commits ------- e3899f5 Fix deprecation message placeholders
…ter (GromNaN) This PR was merged into the 5.4 branch. Discussion ---------- [FrameworkBundle] Add framework config for DBAL cache adapter | Q | A | ------------- | --- | Branch? | 5.4 | Bug fix? | yes | New feature? | no | Deprecations? | no | Tickets | doctrine/DoctrineBundle#1417 | License | MIT | Doc PR | - The framework configuration was missing from #43362. Additionnaly, the depreciation message on `PdoCacheAdapterDoctrineSchemaSubscriber` must be removed. This class needs to be used in 5.4 whenever a `PdoAdapter` is used, because it could have a DBAL connection and we need to keep the deprecated behavior. A depreciation message is already triggered in the `PdoAdapter` itself when it gets a DBAL connection. Commits ------- 672545d Add framework config for DBAL cache adapter
This PR was merged into the 5.4 branch. Discussion ---------- [Cache] Split PdoAdapter to DoctrineDbalAdapter In Symfony 5.4, the `PdoAdapter` is split and `DoctrineDbalAdapter` is created. | Q | A | ------------- | --- | Branch? | 5.4 | Tickets | Fix symfony/symfony#42962 | Code PR | symfony/symfony#43362 Commits ------- 68fed1b [Cache] Split PdoAdapter to DoctrineDbalAdapter