Content deleted Content added
m Added internal link to "Primitive data type" in the Code and cross-reference check section. |
m Added internal link to "Database" |
||
| (2 intermediate revisions by the same user not shown) | |||
Line 9:
Data validation is intended to provide certain well-defined guarantees for fitness and [[data consistency|consistency of data]] in an application or automated system. Data validation rules can be defined and designed using various methodologies, and be deployed in various contexts.<ref>[https://ec.europa.eu/eurostat/cros/system/files/methodology_for_data_validation_v1.0_rev-2016-06_final.pdf Methodology for data validation 1.0]</ref> Their implementation can use [[declarative programming|declarative]] [[data integrity]] rules, or [[imperative programming|procedure-based]] [[business rules]].<ref>[http://msdn.microsoft.com/en-us/library/aa291820(VS.71).aspx Data Validation, Data Integrity, Designing Distributed Applications with Visual Studio .NET]</ref>
The guarantees of data validation do not necessarily include accuracy, and it is possible for [[data entry]] errors such as misspellings to be accepted as valid. Other clerical and/or computer controls may be applied to reduce inaccuracy within a system.
==Different kinds==
Line 18:
* Range and constraint validation;
* Code and cross-reference validation;
* [[Structure validation|Structured validation]]; and
* Consistency validation
Line 84:
;Referential integrity
:Values in two relational [[database]] tables can be linked through foreign key and primary key. If values in the foreign key field are not constrained by internal mechanisms, then they should be validated to ensure that the referencing table always refers to a row in the referenced table.
;Spelling and grammar check
| |||