> friends: dbQuery("select * from firends where user_id = "+userId).data,
> comments: dbQuery("select * from comments where user_id = "+userId).data,
> likes: dbQuery("select * from likes where user_id = "+userId).data
I'm no js developer, but there has to be a way of using prepared statements, even if just for sample code.
It's not 2001 anymore, security is important!
This can be done, for example, by testing it before the SQL call. In that case, it's safer than most pointer-dereferences done in C++.
>friends: dbQuery("select * from firends where user_id = "+userId).data
The point is that regardless of where it came from parameterized queries are a staple of programming now, and having an example without it would be like having an example of a login system be
if (username in db && password in db) { login() }There are valid cases where you're sure that the thing you're looking at is a valid id (ie. you already pulled it out of the database or by generating it yourself), not every program is a webapp that's handling user input, and examples like this aren't meant to teach you best security practices.
And yes the login system example would be acceptable if you're discussing something entirely unrelated to actually implementing one.
dbquery('select * from friends where user_id = $1', userId)
And the benefits of prepared or parameterized statements don't end at security, they can often have performance benefits as well.
And as for the login pseudocode, if it doesn't have anything to do with the example, hide the implementation:
if (userIsAuthenticated === true) { login() } dbquery(sql`select * from friends where user_id = ${userId}`)
Template strings are the one ES2015 feature I still really haven't used much. And this almost seems like a textbook use case for them! I'll need to give this a shot in a toy project and see if I can't get my own version hacked together for support with my favorite database interface library in node (pg-promise)