Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Removed support for older Doctrine versions #1612

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

Merged
merged 2 commits into from
Jan 27, 2016

Conversation

stof
Copy link
Member

@stof stof commented Sep 26, 2014

The minimal versions are now Doctrine Common 2.3, Doctrine ORM 2.4 and Doctrine MongoDB ODM 1.0-alpha10.

I just figured out that CouchDB does not yet rely on the Doctrine Common events yet, so I will need to change this partially (I was in the train when doing it, without access to github to check it).
I'm wondering whether I revert the removal of the CouchDB dedicated listener, or whether I update the ODM and try to convince @beberlei to release a new version instead. I don't know how many people use the CouchDB integration in the bundle.

@stof stof added this to the 2.0 milestone Sep 26, 2014
@stof stof changed the title Removed support for older Doctrine versions [WIP] Removed support for older Doctrine versions Sep 26, 2014
@stof stof force-pushed the doctrine_versions branch from 6cfaada to 7e5fb85 Compare September 26, 2014 22:44
@merk
Copy link
Member

merk commented Sep 27, 2014

👍

1 similar comment
@sstok
Copy link

sstok commented Sep 28, 2014

👍

@stof stof force-pushed the doctrine_versions branch from 7e5fb85 to 47d6906 Compare October 28, 2014 14:57
@stof stof changed the title [WIP] Removed support for older Doctrine versions Removed support for older Doctrine versions Oct 28, 2014
@stof stof removed the in progress label Jan 19, 2015
@stof stof force-pushed the doctrine_versions branch from 47d6906 to f8b69f9 Compare June 1, 2015 09:52
stof added 2 commits January 27, 2016 01:32
The minimal versions are now Doctrine Common 2.3, Doctrine ORM 2.4 and
Doctrine MongoDB ODM 1.0-alpha10.
It duplicates the logic rather than extending the class to allow having
clean typehints in the future-proof class.
@stof stof force-pushed the doctrine_versions branch from f8b69f9 to d3fc0f8 Compare January 27, 2016 00:32
@stof stof merged commit d3fc0f8 into FriendsOfSymfony:master Jan 27, 2016
stof added a commit that referenced this pull request Jan 27, 2016
This PR was merged into the 2.0.x-dev branch.

Discussion
----------

Removed support for older Doctrine versions

The minimal versions are now Doctrine Common 2.3, Doctrine ORM 2.4 and Doctrine MongoDB ODM 1.0-alpha10.

I just figured out that CouchDB does not yet rely on the Doctrine Common events yet, so I will need to change this partially (I was in the train when doing it, without access to github to check it).
I'm wondering whether I revert the removal of the CouchDB dedicated listener, or whether I update the ODM and try to convince @beberlei to release a new version instead. I don't know how many people use the CouchDB integration in the bundle.

Commits
-------

d3fc0f8 Re-added a dedicated listener for CouchDB
910b668 Removed support for older Doctrine versions
@stof stof deleted the doctrine_versions branch January 27, 2016 00:39
@merk
Copy link
Member

merk commented Jan 27, 2016

I'm not sure if it's just my weird setup in an older project, but the compiler is removing the fos_user.doctrine_registry alias even though it is being used by the ORM fos_user.object_manager service.

app/cache/de_/ap_DevDebugProjectContainerCompiler.log after a composer upgrade and a failed cache:clear:

Symfony\Component\DependencyInjection\Compiler\RemovePrivateAliasesPass: Removed service "fos_user.doctrine_registry"; reason: private alias

The service definition in app/cache/de_/ap_DevDebugProjectContainer.xml:

    <service id="fos_user.object_manager" class="Doctrine\Common\Persistence\ObjectManager" public="false">
      <argument>null</argument>
      <factory service="fos_user.doctrine_registry" method="getManager"/>
    </service>

@stof
Copy link
Member Author

stof commented Jan 27, 2016

@merk this may be a bug in Symfony failing to detect that a factory is using the service (or failing to inline the factory itself)

@stof
Copy link
Member Author

stof commented Jan 27, 2016

I'm planning another change (hopefully for tomorrow evening but I cannot guarantee it) where I would inject the registry rather than the manager, which would keep the ORM lazy and would also be compatible with resetting the entity manager. This would remove this pattern here (but it would still be good to identify a bug in Symfony)

@xabbuh
Copy link
Member

xabbuh commented Jan 27, 2016

see symfony/symfony#17554 for the fix in Symfony

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants
Morty Proxy This is a proxified and sanitized view of the page, visit original site.