Type safety is not being adhered on insert queries

[dvrfluxchat]

I have a insert query in my db which looks like this and I am using the typescript version of supabase-js.

await supaServiceClient
        .from("table_name")
        .insert({
          column1:value,
          column2:value,
          column3:value
        });

I changed the column "column1" to "newColumn1" but the above query did not throw any errors where there is no "column1". This lead to issues in production where this query stopped working as the insert was failing saying there is no column1 but the compiler did not throw any error. Is this the expected behaviour? If so how do i ensure to get compile time warnings for such scenarios.

[tecoad]

I have the same issue. Did you find out @dvrfluxchat ?

[FilipPano]

I am experiencing the same issue. There is no type safety on insert for values that are not part of your table schema.

E.g

const {data, error} = await supaServiceClient
        .from("table_name")
        .insert({
          column1:value, // this exists as a column in table_name
          column2:value, // this exists too
          column3:value // this does not
        }).select("*");

I think It should throw a type error letting you know that there is no column3 column in your table.

[Lambtsa]

A little irritating that queries are not typesafe automatically if the dbClient is typed but the queries are generic so passing in a type definition will solve this issue

export const insertCountry = async () => {
  return await supabaseClient
    .from('country')
    .insert<UpsertCountryInput>([
      { name: 'Nepal' },
      { name: 'Vietnam' },
    ]);
};

[avallete]

Still seems to be an issue where extra invalids parameters are juste silently dismissed if the object have all the other properties it need:

I'm not sure this is really a bug tough or an intended behaviour, I can see this come handy if you have things like:

  const res = await postgrest
    .from('users')
    .insert({
      ...someObjectWithExtraKeys
    })