You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.The text was updated successfully, but these errors were encountered: