4 ms·
For something other than a webapp, sure. If you're writing a webapp, I suppose I would suspect that you just haven't spent enough time with a good ORM. It's n
by cjbprime 8y ago
For something other than a webapp, sure.
If you're writing a webapp, I suppose I would suspect that you just haven't spent enough time with a good ORM. It's natural to get frustrated with it occasionally, but seems like you can drop to SQL for those cases as a one-off, rather than discard the ORM totally?
- thymanl23 8y agoHmm, yeah, but I think more than just not using a query building api, I prefer pure result objects. Even when dropping to SQL, the result objects are still database-aware objects. I prefer distinct layers between the business domain layer and the data access layer. Having a data access layer return pure business objects allows for this decoupling, but maybe I'm being to strict and forcing a distinction where there doesn't need to be one?