Some Doctrine 2 Extensions
This package contains extensions for Doctrine 2 that hook into the facilities of Doctrine and offer new functionality or tools to use Doctrine 2 more efficently. This package contains mostly used behaviors which can be easily attached to your event system of Doctrine 2 and handle the records being flushed in the behavioral way. List of extensions:
- Tree - this extension automates the tree handling process and adds some tree specific functions on repository. (closure or nestedset)
- Translatable - gives you a very handy solution for translating records into diferent languages. Easy to setup, easier to use.
- Sluggable - urlizes your specified fields into single unique slug
- Timestampable - updates date fields on create, update and even property change.
- Loggable - helps tracking changes and history of objects, also supports version managment.
Currently these extensions support Yaml and Annotation mapping. Additional mapping drivers can be easy implemented using Mapping extension to handle the additional metadata mapping.
Notice: from now on there is only one listener per extension which supports ODM and ORM adapters to deal with objects. Only one instance of listener is required, and can be attached to many different type object managers, currently supported (ORM or ODM)
Recently where was a change for type hinting on object manager and other. These changes requires doctrine2 from master branch. If you do not want to update your doctrine libraries use these extensions from separate branch doctrine2.0.x or simply checkout to this branch.
- Tree closure strategy was refactored and now fully functional. I recommend to use it on huge trees which do not care about ordering of nodes, like file-folder tree for instance.
- Also there are good news for ODM users, @mtotheikle is working on materialized path strategy for ODM Tree like documents.
- Translation query walker is a killer feature for translatable extension. It lets to translate any query components and filter or order by translated fields. I recommmend you to use it extensively since it is very performative also.
- Tree nestedset was improved, now all in memory nodes are synchronized and do not require
$em->clear()all the time. If you have any problems with new feature, open an issue.
- Extensions now use only one listener instance for different object managers
ODM MongoDB support
List of extensions which support ODM
All these extensions can be nested together. And most allready use only annotations without interface requirement to not to aggregate the entity itself and has implemented proper caching for metadata.
Notice: extension tutorial on doctrine blog is outdated. There is a post introducing to these extensions on doctrine project
You can test these extensions on my blog.
All tutorials for basic usage examples are on my blog also.
- Use Symfony/Component/ClassLoader/UniversalClassLoader for autoloading these extensions, it will help to avoid triggering fatal error during the check of class_exists
Running the tests:
PHPUnit 3.5 or newer is required. To setup and run tests follow these steps:
- go to the root directory of extensions
- run: git submodule update --init
- run: phpunit -c tests
- optional - run mongodb in background to complete all tests