3 ms·
That's essentially building an ORM (well, a data mapping layer) out of PL/SQL functions rather than your main language. Why would that be better?
by icebraining 10y ago
That's essentially building an ORM (well, a data mapping layer) out of PL/SQL functions rather than your main language. Why would that be better?
- TimJYoung 10y agoI think he's saying that there was a lot of duplication in the client SQL for various applications (copy/paste, probably). Using SQL functions/procedures/views to return the same result sets would eliminate the duplication and provide "one true source" for such queries. Plus, it would reside in the actual database, allowing it to be portable and not requiring any extra work in the client applications.
- fnord123 10y agoYes, exactly. Also, tables could be refactored without having to update clients.
- ajuc 10y agoTo play devil's advocate - PL/SQL is much closer to SQL than Java/C#/C++/.... The impedance mismatch between relational and OO is much bigger.