Known Issue: Validation only checks one unique constraint per row


If you have two or more columns with unique constraints, when you validate the table, only one unique constraint will be tested per row.

In this situation, if you fix all reported errors and validate again, new errors may be reported.


  1. Fix all reported errors
  2. Validate
  3. Repeat until there are no more errors

Data Curator Issue

The technical aspects of this known problem are discussed in Data Curator issue #476 on GitHub.

Planned Resolution Date


Data Curator uses the Frictionless Data tableschema-js software library for data validation. Full validation is not performed so response times are acceptable. If this library is improved, then this issue may be resolved.