Closed andrewmclagan closed 9 years ago
I'm pretty sure this has already been proposed, and isn't going to happen. Laravel's database component is already the single most difficult component to maintain as it is.
Noted. I thought as much. maybe possible in the far future.
If you're very interested in this idea, there's no reason why you can't start such a project. Good luck if you do. :)
haha.. thanks I would need it. Im actually in the process of booting an open source Laravel based e-commerce package eco-system... maybe one day.
Yeh. There's never enough time for everything. :)
Firstly I'm aware of the scope and implications of this feature request. Secondly I'm aware of the existence of Doctrine.
I propose an ORM layer that follows the data mapper pattern with an "eloquent like" syntax and API.
For larger applications the maintainability, performance and adherence to single responsibility becomes difficult to achieve whilst following the active record pattern, as Eloquent does. I believe it would be immensely valuable to the community to have a data mapper ORM layer built with the Laravel "paradigm" in mind, using an API and syntax that the community has become accustom to.