Making field required if there are empty/null cells bring the application to inconsistent state

[roll]

Overview

sqlalchemy.exc.IntegrityError: (sqlite3.IntegrityError) NOT NULL constraint failed: players.Golden Balls
[SQL: INSERT INTO players ("_rowNumber", "_rowValid", "Name", "Golden Balls") VALUES (?, ?, ?, ?)]
[parameters: [(2, 1, 'Lionel Messi', 6), (3, 1, 'Cristiano Ronaldo', 5), (4, 1, 'Franz Beckenbauer', 2), (5, 1, 'Michel Platini', 1), (6, 1, 'Johan Cruyff', 1), (7, 1, 'Marco van Basten', 1), (8, 1, 'Ronaldo Nazario', 2), (9, 1, 'Zinedine Zidane', 1), (10, 1, 'Ronaldo', 2), (11, 0, 'Ronaldinho', None)]]
(Background on this error at: https://sqlalche.me/e/20/gkpj)

Plan

• [x] PR frictionless-py to have a flag for the index function that will tell the library not to create NOT NULL constraint on any fields (even though it's required by the Table Schema constraints) (see the mapper)
• [x] update frictionless-py dependency
• [x] use this flag in the file/index endpoint