query: Prevent harmful call to database on string
positive_passages.docid: 158241
positive_passages.text: Will using LINQ to SQL help prevent SQL injection
negative_passages.docid: 82084
negative_passages.text: Restrict passed parameter to a string literal
negative_passages.docid: 91049
negative_passages.text: How to restrict a column value in SQLite / MySQL
negative_passages.docid: 26591
negative_passages.text: How to prevent users from killing C# Application
negative_passages.docid: 34175
negative_passages.text: Create a method call in .NET based on a string value
negative_passages.docid: 158391
negative_passages.text: Most efficient way to check for DBNull and then assign to a variable?
negative_passages.docid: 39700
negative_passages.text: Escape a string in SQL Server so that it is safe to use in LIKE expression
negative_passages.docid: 152695
negative_passages.text: Is there a MySQL feature like SQL Server 2005's TRY/CATCH blocks?
negative_passages.docid: 108880
negative_passages.text: Handle "potentially dangerous Request.Form value..."
negative_passages.docid: 34449
negative_passages.text: Trigger for avoid insertion from data loader?
negative_passages.docid: 122816
negative_passages.text: SQL injection with php filtering
negative_passages.docid: 46503
negative_passages.text: Do htmlspecialchars and mysql_real_escape_string keep my PHP code safe from injection?
negative_passages.docid: 141091
negative_passages.text: How can sanitation that escapes single quotes be defeated by SQL injection in SQL Server?
negative_passages.docid: 44264
negative_passages.text: identify and execute php code on a string
negative_passages.docid: 123619
negative_passages.text: Shouldn't mysql_real_escape_string() leave slashes in Database?
negative_passages.docid: 33700
negative_passages.text: Stop SQL query execution from .net Code
negative_passages.docid: 39060
negative_passages.text: Classic ASP SQL Injection Protection