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
.insert and .upsert do not warn if the object includes a nonexistent column, whereas TablesInsert type used directly does
.insert
.upsert
TablesInsert
postgrest.from("users").insert({ name: "James", i_dont_exist: "xyz" })
does not error even if
const payload: TablesInsert<"users"> = { name: "James", i_dont_exist: "xyz", };
would
The insert/upsert methods would cause type errors when passing nonexistent columns
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Bug report
Describe the bug
.insert
and.upsert
do not warn if the object includes a nonexistent column, whereasTablesInsert
type used directly doesTo Reproduce
does not error even if
would
Expected behavior
The insert/upsert methods would cause type errors when passing nonexistent columns
System information
The text was updated successfully, but these errors were encountered: