🎉 Write safer code with new vulnerability prevention features in GitHub Copilot 🔒 ✅
to prevent sql injection a better approach is to use store procedures and avoid types like strings in params to pass into the stores procedures (sometimes just cant and its ok), with this you can avoid build "queries everywhere" in your backend repo (what happen if your table change the name or just delete one column?, is going to fail everywhere :O), also you can use some good lib utility to call this SP, usually they cover security breaches, another approach is just use an ORM solution, but this is another thing. IMHO :)
Ezekiel Zary
1y
Navarre Trousselot there is a solution to CoPilot suggestions of other people's code (including API keys) GitHub must retrain a completely new model only on open-source licensed code. We do that...
Ido Tzur Tal
1y
Itay Hayun אחי זה אתה
ROCIO HERRERA O
6mo
GRACIAS POR EL MATERIAL ENVIADO A MI CORREO ELECTRONICO ROCIO HERRERA OBESO GRUPO MANAJECTMENT INTERNACIONAL GLOBAL
Yi leng Yao
1y
Use jOOQ, thank me later.
Reeh Martins
1y
Aprende Johnny kkkkk qnt mas conhecimento melhor kkkk
Sama Mansori
6mo
چجوری؟
Mikael R.
1y
Very useful
Como ficiona
Founder of Navexa, empowering investors to track performance, calculate taxes, and build wealth. Sharing fintech and investing insights.
1yThis needs to go a bit further. Co-pilot has been writing out peoples API keys for various different services. I got auto recommended someones mixpanel api key a couple of days a go.