Follow up of
Repository configuration regarding DBAL connection should integrate correctly with DoctrineBundle.
- More standard approach, Symfony wise.
- Allow developers to seamlessly use Doctrine ORM
- Simplifies configuration in ezpublish.yml
DoctrineBundle uses the concept of connections which are re-usable. Idea is to make it possible to use a defined connection:
# Using Doctrine default connection
# Takes all default values (engine: legacy, connection: default)
# Optional, if not provided, will take the first defined repository by default
# Using a named Doctrine connection
# legacy => Legacy storage engine
Also, if no connection is configured, it would use the default one.
For a developer to reuse this connection in his code for his ORM needs, it would be as simple as:
class SomeController extends Controller
public function indexAction()
$em = $this->getDoctrine()->getManager( 'my_doctrine_connection' );