Use columns query parameter for insert

[steve-chavez]

Feature request

With the columns query parameter, the All object keys must match error message is avoided. Instead the direct PostgreSQL error is shown, which is more helpful for debugging.

Example:

// When making a bulk insert
const { data, error } = await supabase
  .from('mytable')
  .insert([
    {
      field: 'val2',
      nonNullableField: 'val3'        
    },
    {
      field: 'val1'     
    }      
])

// Right now this happens
console.log(error);
{message: 'All object keys must match'}

// If we were to use the columns query param, we'd get a clearer error
console.log(error);
{
    "code": "23502",
    "details": "Failing row contains (val1, null).",
    "hint": null,
    "message": "null value in column \"nonNullableField\" violates not-null constraint"
}

Note: This doesn't solve #173 because the default value of the columns won't be applied. It would still clear the error message though.

Possible implementation

Is not necessary to add a new method to the lib. Internally, the body of the bulk insert can be passed through a function that gets the keys and produces the columns query param.

Something like:

let body = [
    {
      field: 'val2',
      nonNullableField: 'val3'        
    },
    {
      field: 'val1',
      anotherField: 'val4'     
    }      
];

// Using https://ramdajs.com/
let columns = R.join(',', R.uniq(R.flatten(R.map(R.keys, body))));

console.log(columns);
"field,nonNullableField,anotherField"
// append this to ?columns= in the http request

[github-actions]

🎉 This issue has been resolved in version 0.28.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀