The DataMapper is not more modern or newer, but just more suited for an ORM. The main reason people change is because ActiveRecord does not make for a good ORM. An AR wraps a row in a database table or view, encapsulates the database access, and adds domain logic on that data. So by definition, … Read more
Plan A: SET FOREIGN_KEY_CHECKS = 0; — Disable foreign key checking. TRUNCATE TABLE forums; TRUNCATE TABLE dates; TRUNCATE TABLE remarks; SET FOREIGN_KEY_CHECKS = 1; — Enable foreign key checking. Plan B: You should truncate child tables firstly, then parent tables. Disabling foreign key checks risks entering rows into your tables that don’t adhere to the … Read more
A few points: It strikes me that overall, you have a good design. That’s evidenced, in part, by the fact that you can make changes in it with little impact on any classes outside of the ones that are changed (low coupling). That said, it’s very close to what Entity Framework does, so while it’s … Read more
Suppose your application manages Person objects, with each instance having name, age and jobTitle properties. You would like to persist such objects, retrieve them from the persistence medium and maybe update (say, on their birthday, increment the age) or delete. These tasks are usually referred to as CRUD, from Create, Read, Update and Delete. It … Read more
Your example terms; DataMapper, DAO, DataTableGateway and Repository, all have a similar purpose (when I use one, I expect to get back a Customer object), but different intent/meaning and resulting implementation. A Repository “acts like a collection, except with more elaborate querying capability” [Evans, Domain Driven Design] and may be considered as an “objects in … Read more