Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

All columns should not be required in the JSON for PUT requests #21

Open
KayEss opened this issue Jan 16, 2019 · 0 comments
Open

All columns should not be required in the JSON for PUT requests #21

KayEss opened this issue Jan 16, 2019 · 0 comments

Comments

@KayEss
Copy link
Member

KayEss commented Jan 16, 2019

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant