Nathaniel Marrin

Added a new configuration directive entity_managers that allows for individual configuration of multiple entity managers. This entry will be created automatically if no entity_managers entry is defined If present each...

@kirkbushel Do you have a list of tests or features you would like tests added for? Since the old configuration is rebuild into the new format the old test should...

@kirkbushell Sorry this took so long. I needed to do a little refactoring in order to make it more testable. Let me know your thoughts on this and / or...

Along with the `entity_managers` a new configuration option `default_connection` was adding in this pass. This will default to the default database in the laravel database configuration but can be changed...

@FoxxMD You are correct. Instead of creating an entity manager for the default database we now create a new entry in $app['config']['doctrine::doctrine'](doctrine.php) called `entity_managers`. This item will be populated automatically...

@FoxxMD \Tests\MultipleEntityManagersAndConnections\SchemaCreateCommandTest uses the following connection information. It will call the command with sqlite to use a non-default entity manager for the operation. For reference the test adds the following...

@FoxxMD You want to replace `use Doctrine\ORM\EntityManagerInterface;` with `use Doctrine\Common\Persistence\ManagerRegistry;` and then replace `EntityManagerInterface $entityManager` with `ManagerRegistry $registry`. This will inject the IlluminateRegistry. EntityManagerInterface is still available for backwards compatibility....