Read ORM in Ruby: An Introduction and learn with SitePoint. Our web development and design tutorials, courses, and books will teach you HTML, CSS, JavaScript, PHP, Python, and more.

The intention of this post is to share the data that I have gathered in researching and experimenting in making domain models 100% ignorant of persistence and making them ORM unaware. This will also…

This series explores a strategy for using Eloquent to easily achieve a DataMapper-like design that improves overall maintainability and readability of medium-to-large applications. Eloquent (and by…

Analogue ORM : Data Mapper ORM for Laravel/PHP

Hydration is the most expensive operation performed by Doctrine ORM: how do we prevent it from killing our applications?

I have been using Doctrine2 for about 3 years now. I started with the first 2.0 stable, integrating it into my employer's in-house framework, and in the last year, I have been using it as part of Symfony2. There are quite a few things that I love about it, and a small amount that I dislike.

In this article, I'm going to cover an example of implementing some business logic in our usual Active Record patterns, and then I'll show how the same logic can be applied using the Data Mapper pattern. In both cases, we'll see how we can move our business logic into our business entities, thus avoiding anemic business domain. We'll also cover pros and cons of the two styles of ORMs and how they affect the way we write our code.

An ORM is a layer that is used to transform data between an application and a database.

Arno Slatius explains Yii 2.0's ActiveRecord, listing the features, novelties, upgrades and usage examples.

The document discusses good practices for using Object-Relational Mapping (ORM) in database development, covering topics such as dependency management, fetching strategies, and querying with DQL (Doctrine Query Language). It provides examples of defining entities, associations, fetching strategies (eager, lazy, extra_lazy), and formulating complex queries with joins. The document emphasizes that improper ORM usage can lead to performance issues, encouraging developers to adhere to established guidelines.