Comment SQL in paired classes is not nirvana (Score 1) 197
We all seem to forget that SQL was supposed to be the data abstraction layer. Somehow it's now this ugly stuff that no one is supposed to touch, and every project that is built attempts to reconstruct a data abstraction layer.
Not to mention that OO abstraction on top of a relational model causes significant complications. How does one perform true joins? By building additional classes that represent the "join" of two other classes? What about complex reporting queries?
Of all the apps that are claimed as "maintainable" because of OO abstraction, I've never seen one that actually accomplishes this in a truly clean way. Because it's hardly ever possible if you're making true use of a relational database.
Not to mention that OO abstraction on top of a relational model causes significant complications. How does one perform true joins? By building additional classes that represent the "join" of two other classes? What about complex reporting queries?
Of all the apps that are claimed as "maintainable" because of OO abstraction, I've never seen one that actually accomplishes this in a truly clean way. Because it's hardly ever possible if you're making true use of a relational database.
