I'm looking to put together a single page web application with many form inputs. I've run into issues with other web pages where there is an ugly SQL error sent to the user if the maxlength constraint of the field in the table was violated. I'd like to know how to manage this type of validation.


  1. Should I put the effort into making sure that the HTML form input is limited in size for every input field (as opposed to targeting significant fields)?

  2. Should the maxlength of the input field be tied programmatically to the constraints of database fields (through a query of the database system tables) or would this be unrealistic?

I'm looking for both what is best practice and what is maintainable (I don't want to have to do a lot of extra work if the database design changes). Is it easier just to decode the SQL error post-submit and inform the user?

Related Questions

use of additional validation like "between 6 and 20 characters" less frequent, as this increases maintenance work on changes

1 Answer 1

  1. Yes, you probably should put maxlength constraints on every field where such constraints exist. The reason for doing that is mainly so that the user can get immediate feedback, instead of having to send the request and having the application tell them that they cannot do that (though that may still happen in some cases);

  2. Attempting to derive maxlength from the database schema is necessarily going to tie the technical database implementation / definition with the front-end HTML - that is, you are going to have, in one form or another, the view generation code be aware of the underlying data structures, and of how the underlying database tables map to the UI. Such a coupling, in my experience, actually increases the burden of introducing a change. It may also yield the wrong value anyway, as HTML5 maxlength is defined in terms of Unicode code points, whereas max length in databases is often defined for UTF-16 or byte length;

In my experience, once the maxlength of some data is set, it should only change rarely, and because of that, the maintenance burden is acceptable.

Also, even if you put maxlength and minlength in the HTML form, you will still need to validate on the server side, because anyone may still send a form with data that would not validate in the HTML form.

  • You bring up a good point about not coupling the front end with the DB implementation. I guess I was concerned about duplicating efforts to manage validation but max length validation should be simple enough to maintain.
    – Chic
    Commented Mar 12, 2015 at 13:35

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.