Replace Kohana's ORM with Laravel's or use Laravel's ORM with Kohana (code provided)

[etopian]

Replace Kohana's ORM with Laravel's or use Laravel's ORM with Kohana (code provided)

[bato3]

Hi!
Replace is not an option!Tell me what should I do with my legacy code?

The only thing that would make sense is to update the documentation that such a module exists and can be installed separately.

[Sebjugate]

Sounds like a great idea, though I definitely agree that this should be an additional module as you've done in your sample code, rather than a replacement of the legacy ORM module.

Because modules can be easily enabled and disabled, I would say that the eloquent module could still be distributed with the main Koseven package for visibility, or even enabled by default in new installs.

[chrisgo]

My opinion is eloquent is kind of hard to use (still don't know how to do deep joins properly personally) and there was a nice ORM package for Kohana called Jelly (original gone, forked here https://github.com/creatoro/jelly).

I was planning on actually making this work inside Laravel so it can use all the Kohana database classes which are awesome (but remove all the CFS so it is closer to normal class loading)