Difference between revisions of "Data Validation"
Barrymavin (Talk | contribs) (→Validation Rules) |
Barrymavin (Talk | contribs) (→Validation Rules) |
||
| Line 9: | Line 9: | ||
It is easy for an end user to make a mistake when they are entering data or even to leave out important details that must be entered, so we need to check this data when it is being entered into the database. | It is easy for an end user to make a mistake when they are entering data or even to leave out important details that must be entered, so we need to check this data when it is being entered into the database. | ||
| − | + | In an business application its not only users who perform CRUD (Create Read Update Delete) operations on data but also external processes such as loading tariffs, prices etc into tables periodically in batch. | |
| + | |||
| + | There must be protections in place to prevent data corruption and invalid data being stored in a database. | ||
| + | |||
| + | This is where validation rules come into play. | ||
==Validation Rules in the UI== | ==Validation Rules in the UI== | ||
Revision as of 09:00, 4 December 2017
Under Construction
Contents
Validation Rules
Validation rules prevent bad data being saved in a table.
Validating data in Lianja allows you to check data whilst it is being entered by the database user and will enable you to not save the data if it breaks any validation rules or routines.
It is easy for an end user to make a mistake when they are entering data or even to leave out important details that must be entered, so we need to check this data when it is being entered into the database.
In an business application its not only users who perform CRUD (Create Read Update Delete) operations on data but also external processes such as loading tariffs, prices etc into tables periodically in batch.
There must be protections in place to prevent data corruption and invalid data being stored in a database.
This is where validation rules come into play.
