We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
nullable fields should be optional in insert types, as they will default to null
null
The text was updated successfully, but these errors were encountered:
fix: nullable fields are optional when inserting
fba3e1c
Fixes: #20
Various bug fixes and minor features (#22)
acd8d68
Fixes: #2 Fixes: #17 Fixes: #18 Fixes: #19 Fixes: #20 Fixes: #21
chore(release): 1.2.0 [skip ci]
8e6c85c
## [1.2.0](v1.1.0...v1.2.0) (2020-12-01) ### Features * support Date objects ([f671230](f671230)), closes [#19](#19) * support LIMIT clause ([4684631](4684631)), closes [#18](#18) ### Bug Fixes * allow 'undefined' for values in update/where ([8ec3fec](8ec3fec)), closes [#17](#17) * columnType is optional ([09c0362](09c0362)), closes [#2](#2) * nullable fields are optional when inserting ([fba3e1c](fba3e1c)), closes [#20](#20) * remove table identifier from UPDATE SET clause ([6dbf930](6dbf930)) * temporarily just snake case columns ([b2c7004](b2c7004)), closes [#21](#21)
🎉 This issue has been resolved in version 1.2.0 🎉
The release is available on:
Your semantic-release bot 📦🚀
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
nullable fields should be optional in insert types, as they will default to
null
The text was updated successfully, but these errors were encountered: