laravel-doctrine
laravel-doctrine copied to clipboard
mitchellvanw
NO LONGER MAINTAINED! A Doctrine 2 implementation that melts with Laravel
Allows for the user to choose the naming strategy. eg. 'naming_strategy' => 'Doctrine\ORM\Mapping\UnderscoreNamingStrategy'
Function isDeleted for SoftDeletes returns true even if value of isDeleted is set to null. This fix changes the return value to false in this case.
Doctrine automatically updates the database schema to represent the entities in your application, thus rendering most of the use-cases for Laravel's migrations useless, however Laravel's migrations can still be useful...
This is useful, if devs want to be able to clear Doctrine's result cache independently from Doctrine's metadata and query caches. This PR requires [this](https://github.com/mitchellvanw/laravel-doctrine/pull/138) PR.
This allows devs to run Doctrine's commands: [link](http://docs.doctrine-project.org/projects/doctrine-orm/en/latest/reference/tools.html#command-overview) using laravel's `artisan`. This doesn't support passing `--` options. But at least it allows to clear the cache.
Add an ability to configure the cache's keys namespace. This is useful if you need extra control over handling key names collisions in your Cache solution.
This is needed so registering new cache providers doesn't involve hacking the project's code. Also, the default cache providers are not even `new'd` when the end user doesn't want to...
Whatever I did, the current code didn't seem to work. I edited it to make it a DQL query. It does work now. Only changes required for this to work...
doctrine::doctrine.proxy.directory is wrong. It doesn't work if I put the path in my doctrine config file. When I deleted doctrine::, it did work. It also makes more sense. Please check...
doctrine::doctrine.proxy.directory gave NULL while doctrine.proxy.directory gave me the directory. Might be worth looking into.
Metadata
Owner
Metadata
NO LONGER MAINTAINED! A Doctrine 2 implementation that melts with Laravel