3 ms·
Most of the time it is not about SQL itself but the interface. Like, since you avoid ORM, you never ran into a mismatch between parameters/query results in pre
by rini17 5y ago
Most of the time it is not about SQL itself but the interface. Like, since you avoid ORM, you never ran into a mismatch between parameters/query results in prepared SQL statement vs. surrounding code? Isn't that a security risk too?
- marcus_holmes 5y agonot so far, no. I usually create a view as a compound result type for functions, and match the struct for the results to the view. So the SQL compiler tells me if I got a return type wrong, and if I need to change the struct then I change the view to match, and the compiler tells me all the other places I need to change.