uno lie u no get a ting lol cuzz me no get it ....o who ever eh dem get it let us all know what de hell it is u get hunnnnnn not a ra**c*atssssssssssssssssssss ting lolol
__________________
26 people die from swine flu & everybody wants 2 wear a mask. 2,000,000 people die from AIDS and nobody wants to wear a condom!
if u kno access u shud kinna get dis but lol his name can be interpreted as a command, ok? and because dem neva...maybe dis will explain it.
The best way to protect against SQL Injection is to sanitize the user's input data before placing it within a SQL query. Sanitizing data is the act of stripping out any characters that we don't need from the data we are supplied. Returning to our username/password example, the username field, say, should only contain alphanumeric characters (and maybe spaces, underscores, etc. depending on your configuration). Importantly, username values (and password values, for that matter) should not contain apostrophes. Sanitizing user input, then, ensures that these user inputs contain only the valid characters. By requiring that the username and password being passed to the database does not contain any invalid characters, we can protect ourselves against a SQL Injection attack.