| ▲ | xigoi 4 hours ago | ||||||||||||||||
The question is why we don’t have database management systems that integrate tightly with the progmming language. Instead we have to communicate between two different paradigms using a textual language, which is itself inefficient. | |||||||||||||||||
| ▲ | runroader 4 hours ago | parent | next [-] | ||||||||||||||||
We tried that in 90’s RAD environments like Foxpro and others. If it fits the problem, they were great! If not, it’s even worse than with an ORM. They rarely fit today since they were all (or mostly) local-first or even local-only. Scaling was either not possible or pretty difficult. | |||||||||||||||||
| ▲ | Shorel 4 hours ago | parent | prev | next [-] | ||||||||||||||||
Because every single database vendor will try to lock down their users to their DBMS. Oracle is a prime example of this. Stored procedures are the place to put all business logic according to Oracle documentation. This caused backslash from escaping developers who then declared business logic should never be inside the database. To avoid vendor lock-in. There's no ideal solution, just tradeoffs. | |||||||||||||||||
| |||||||||||||||||
| ▲ | ivan_gammel 4 hours ago | parent | prev [-] | ||||||||||||||||
The answer is simple: model optimized for storage and model designed for processing are two different things. The languages used to describe and query them have to be different. | |||||||||||||||||
| |||||||||||||||||