2 ms·
> "There should be no way to build and use an invalid query" Well the SQL server won't actually run an invalid query, so what's your point? I'm not afraid of
by mantrax5 12y ago
> "There should be no way to build and use an invalid query"
Well the SQL server won't actually run an invalid query, so what's your point?
I'm not afraid of invalid queries. I'm rather afraid of valid queries like these:
"DELETE FROM Table"
Because depending on how abstract your ORM is, it's far easier to run something you really don't want to run on your SQL server. But at least it'll be valid, hey!
- mercurial 12y ago> Well the SQL server won't actually run an invalid query, so what's your point? To avoid runtime errors, I suppose. As for "DELETE FROM table", I would say it's not any likelier to happen with an ORM than without. I haven't experienced issues of this sort, at least. The problem is more to build efficient, complex SELECT queries without getting a bad surprise performance-wise once in production.