Eloquent VS Laravel

I'm not going to pretend that my improvements will land in the official Laravel code any time soon, or ever. So I am going to use the illuminate/database repository. Because it is a sub module of the laravel/framework this has a few problems. The biggest problem is that there are no tests.

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)

The method was contributed by @devajmeireles in PR #55815.

In Laravel, inheritance plays a key role in the framework’s core architecture. A clear example is the Application class, which extends the Container class. This relationship allows Laravel’s application instance to inherit all the powerful features of the service container—such as dependency resolution and binding—while adding its own framework-specific logic.

Let’s take a real-life example of attributes. Laravel 11 introduced contextual attributes and for our example we will be using the Config attribute. The #[Config(...)] attribute allows you to annotate a constructor or method parameter, so that Laravel’s service container can resolve and inject the corresponding config value at runtime:

For databases that have relations between entities, I would move those to the Builder class, instead of in the model currently. I think the with methods could do the trick with a bit a of modification. And adding a to method for nested inserts.

A few days ago, Litvinchuk added the method withRelationshipAutoloading in PR #53655. As explained in the merge description, it checks the relationships you're calling and applies Auto Eager Loading to them. Of course, this method only exists in v12.8, so I decided to add it to earlier versions in case I work on a project that uses a version before that. 🔥

I'm not going to pretend that my improvements will land in the official Laravel code any time soon, or ever. So I am going to use the illuminate/database repository. Because it is a sub module of the laravel/framework this has a few problems. The biggest problem is that there are no tests.

Looking at artisan and the Symfony maker bundle, I saw two different ways to build content. Artisan works with stub files which are text files with a Twig syntax for the variables. And the maker bundle works with php templates.

In PR #51376 to Laravel in May 2024, Jason McCreary and Joel Clermont added the Illuminate\Console\Prohibitable trait to the framework, which was then included in the Laravel 11.9 release.

When you call the driver method on the facade, it's proxied to a manager, depending on which facade you're using. In the caching scenario, it's directed to the CacheManager. Let's inspect its code.

For more information on this vulnerability, check out the official Laravel security advisory: GHSA-gv7v-rgg6-548h