Because your database contains sensitive information, hackers may attempt to use your form to submit malicious commands to your backend database.If you are using a My SQL database, this is called My SQL Injection.That behaviour can be irritating when clicking through demos of the validation plugin – it is designed for an unobtrusive user experience, annoying the user as little as possible with unnecessary error messages.So when you try out other demos, try to react like one of your users would, and see if the behaviour is better then.If not, please let me know about any ideas you may have for improvements! Throughout the documentation, two terms are used very often, so it's important that you know their meaning in the context of the validation plugin: The validate method returns a Validator object that has a few public methods that you can use to trigger validation programmatically or change the contents of the form.The validator object has more methods, but only those documented here are intended for usage.All credit cards are 16 digits and the 16th digit can be calculated based on the first 15 numbers.This means you can use Java Script to check for, and alert the user to, credit card typos.
If you validate the form using j Query, you can notice this and alert the user to their mistake instead of submitting the form.To avoid this problem, you must validate form submissions using your server.You cannot rely on Java Script to avoid this security problem. You can also download this demo and check out the source as we go through this tutorial.Of course that isn't the only way to specify rules.
You also don't have to rely on those default messages, but they come in handy when starting to setup validation for a form.
There are two types of validation: client side validation and server side validation.