3 ms·
Agree with you that the problem is more on language side, I also believe that the problem isn't as bad as it seems with the right tooling. For example I recent
by takeda 7y ago
Agree with you that the problem is more on language side, I also believe that the problem isn't as bad as it seems with the right tooling.
For example I recently discovered that I can configure PyCharm to a database. Interestingly, after I did just that, the IDE downloaded the database schema and suddenly I got highlighting, autocomplete and refactoring available (well as migrations).
Suddenly I felt like I didn't actually need an ORM.
C# seems to also have thing called LINQ I'm not as familiar with it but my understanding is that it is a language within language that can represent SQL statements. I'm guessing this might be what you're talking. Ultimately I think the solution is that:
- there's a way to efficiently express what data we need (ORM has the issue you mentioned)
- an IDE can understand this syntax so it can help with it the same as with rest of the code.
- gwbas1c 7y agoLINQ lets you query and filter collections. You're thinking of LINQ to SQL.
- cwbrandsma 7y agoI don’t think that is used much anymore. Most shops I’ve been on moved to Entity Framework. Uses a very similar syntax tho.
- gwbas1c 7y agoThe few times I looked at LINQ to SQL, it didn't meet my requirements. The first time it had the "update" problem, meaning, it appeared that I had to always load an object into memory before updating it. (2008) The second time, it wasn't available in Mono. (2011) Granted, a lot changed since
- takeda 7y agoI see, I never used it myself, from the outside it looked promising it is sad that it didn't deliver.