3 ms·
There are patterns to resolve this. Depending how you structure your DAL, your data access classes can provide transaction handles. It's a data access layer, yo
by mvdtnz 3y ago
There are patterns to resolve this. Depending how you structure your DAL, your data access classes can provide transaction handles. It's a data access layer, you don't need to abstract away the fact that you're dealing with a database.
- paulryanrogers 3y agoIME young businesses evolve so quickly too much abstraction is a higher risk that some bleeding among DAL and business rules.
- edgyquant 3y agoHow is this not just a hand rolled ORM?
- JohnBooty 3y agoAn ORM is a specific kind of data layer. It is general-purpose, and as the name suggests, it is an Object-Relational Mapper whose primary purpose is to map relations to objects and vice-versa. So no, bespoke data access layer code is not an ORM.
- jakelazaroff 3y agoI mean, yeah, but the patterns all look like the thing you said you don’t accept in your own applications: “something like a query builder that allows different parts of the application to work together to lazily compose queries”.