Support different fields in insert

[Magnuti]

Bug report

• I confirm this is a bug with Supabase, not with my own application.
• I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

Having a table that looks like this

CREATE TABLE IF NOT EXISTS "public"."items" (
    "id" "uuid" DEFAULT "gen_random_uuid"() NOT NULL,
    "user_id" "uuid" NOT NULL,
);

When inserting new items in bulk with different fields (id only present on one item)

await supabaseClient.from("items").insert([
    {
        id: randomUUID(),
        user_id: userId,
    },
    {
        user_id: userId,
    },
])

Both items should be inserted; one with the provided id and one with a random UUID as id.

However I get this error

{
  code: "23502",
  details: "Failing row contains (null, e40a9b26-2a32-429f-ae71-9fada8ed4a33),
  hint: null,
  message: 'null value in column "id" of relation "items" violates not-null constraint'
}

It seems that gen_random_uuid is ignored.

To Reproduce

Follow the steps above.

Expected behavior

Both items should be inserted; one with the provided id and one with a random UUID as id.

Additional context

Both this

await supabaseClient.from("items").insert([
    {
        user_id: userId,
    },
    {
        user_id: userId,
    },
])

and this works

await supabaseClient.from("items").insert([
    {
        id: randomUUID(),
        user_id: userId,
    },
    {
        id: randomUUID(),
        user_id: userId,
    },
])

The solution here is to split the insert operation into two bulk inserts; one where id is present on all items and another where id is absent on all items. But this seems like a hack.

[Magnuti]

This seems to be handled well in the Swift library after a similar bug was found there supabase/supabase-swift#203 (comment)