All columns should not be required in the JSON for PUT requests #21
Description
Right now it seems that any column mentioned in the PUT configuration of the fostgres.sql view is required in the JSON data submitted even if the column is nullable in the database. Whether a column is needed or not should really be a matter of schema validation and ultimately the database.
I would like to fix it so that if a column is mentioned in the configuration, but is not present in the JSON then it also will not be mentioned in the INSERT statement that is generated.