I’d say that if you aren’t dealing with objects there’s little point in using an ORM. If your relational tables/columns map 1:1 with objects/attributes, there’s not much point in using an ORM. If your objects don’t have any 1:1, 1:m or m:n relationships with other objects, there’s not much point in using an ORM. If … Read more
Alternatively, you can use one query with a lookup: var lookup = new Dictionary<int, Course>(); conn.Query<Course, Location, Course>(@” SELECT c.*, l.* FROM Course c INNER JOIN Location l ON c.LocationId = l.Id “, (c, l) => { Course course; if (!lookup.TryGetValue(c.Id, out course)) lookup.Add(c.Id, course = c); if (course.Locations == null) course.Locations = new List<Location>(); … Read more
To explain it simply, when you are loading an entity and if it has an association with one or more entities, what should doctrine do? If the association is marked as EAGER, it will fetch and load the associated entity as well. If the association is marked as LAZY, doctrine will create proxy objects (dummy … Read more
Let’s say you have a collection of Car objects (database rows), and each Car has a collection of Wheel objects (also rows). In other words, Car → Wheel is a 1-to-many relationship. Now, let’s say you need to iterate through all the cars, and for each one, print out a list of the wheels. The … Read more