News for hackers. Stuff that matters.

A comment on Gitlab 500 error. Parent comment

Re:Gitlab 500 error by mateo411 on Tuesday June 12, 2018 @01:57PM (#17295956)
I prefer the control of writing SQL too. However, you have to be careful of SQL injection attacks.

Honestly, if you are developing a web app, when you have it working, part of the routine should be to look at the SQL queries for each operation and spot any N+1 issues. I use Django, so this is easy to do in Django Debug toolbar. I'm sure similar tooling exists in other frameworks as well.

[ Parent | on HN ]
Re:Gitlab 500 error by isostatic on Tuesday June 12, 2018 @02:05PM (#17296053)
> you have to be careful of SQL injection attacks.

Surely you're using prepared statements?!

[ Parent | on HN ]
Re:Gitlab 500 error by mateo411 on Tuesday June 12, 2018 @05:20PM (#17298134)
I've string interpolated SQL queries before... I know

I'll only do this for internal apps, not for anything on the public internet. This is not a good practice.

[ Parent | on HN ]