Atlas.Orm VS Eloquent

I'm sure Atlas would compare favorably here.

On second reading, I begin to think that parts of it also apply to Data Mapper implementation practices I see in the wild. I'll need to think about that some more, and perhaps apply the lessons to Atlas.

It was that article that inspired me to put together Atlas.

That's just what Doctrine does, as does Atlas.

Perhaps Atlas would be more to your liking.

> People always seem to ignore the third option: using an ORM that embraces SQL!

I had a similar revelation several years ago, based on the distinctions between a "domain model" and "persistence model" described by Mehdi Khalili, resulting in Atlas for PHP: http://atlasphp.io

Eloquent (docs for query builder and ORM) or Doctrine (docs for (ddbal query builder) and ORM - note, these are separate libraries, but the ORM includes dbal).

You can use the database component: https://github.com/illuminate/database

A similar example: in Laravel's codebase, every line in a doc block is 3 characters shorter than the line above it.

Example: https://github.com/illuminate/database/blob/master/Eloquent/...

View on GitHub

In this case, getting started might be rough unless you know Laravel well, because there's not even a readme there (in contrast to e.g. https://github.com/illuminate/database#illuminate-database which has a clear guide how to use it)