Updating multiple records in Supabase

Armand · 2024-08-06T09:14:39.788+00:00

I'm trying to update several records in my Supabase database with the Toddle API (using POST).I've watched the Toddle.dev todo app YouTube video. So I understand how to update 1 record. But I'm struggling to figure out how to update multiple records.I have a variable with array of objects. Each object has an ID that corresponds with the ID column in the Supabase table I'm trying to update.This is what I have right now (see image).Does anyone have any idea how I should tell Supabase how to identify each object? Thanks in advance

Armand
1 year ago
I'm trying to update several records in my Supabase database with the Toddle API (using POST).

I've watched the Toddle.dev todo app YouTube video. So I understand how to update 1 record. But I'm struggling to figure out how to update multiple records.
I have a variable with array of objects. Each object has an ID that corresponds with the ID column in the Supabase table I'm trying to update.

This is what I have right now (see image).

Does anyone have any idea how I should tell Supabase how to identify each object?

Thanks in advance 🙏
✅1
Mighty
1 year ago
I think you need to use upsert
Mighty
1 year ago
supabase ai says you can send a header named x-upsert with the value true. Have a try if that works.
@Mighty
supabase ai says you can send a header named x-upsert with the value true. Have a try if that works.
Armand
1 year ago
I was already using POST instead of PATCH because I thought the same (to use Upsert).
I added x-upsert to the header, but I still get the same error. Or did I add it in a wrong manner?
Mighty
1 year ago
Hmm :/
Do you only want to update or also create if does not exist?
Tod
1 year ago
Great energy @Armand! Your continuous contribution to the toddle Community just made you advance to Community Level 5!
@Mighty
Hmm :/
Armand
1 year ago
They all exist. So it doesn't really matter I suppose
Tom Ireland
1 year ago
@Armand - It looks like you might need to specify that there could be conflicts for tables with constraints.

I've not done bulk updates but I think you need to specify about merging duplicates.

Looking at the API reference in Supabase (bash against the table list for my app), you might need to pass along an additional header: "Prefer: resolution=merge-duplicates"

Don't quote me on that but that should handle existing updates in bulk and insert new records for new ones if using upsert. 🤞
Maybe backup the table before you try that. 😉
See https://supabase.com/docs/reference/javascript/upsert
Tom Ireland
1 year ago
I think you can use POST for upsert and not worry about that additional header you added. I don't see that listed in the API reference for bash against the table.
Tom Ireland
1 year ago
@Max - I think I saw you started typing, so do shout if you are confident of a solution. 🙂
Max
1 year ago
I don't know the answer, so I stopped typing when I saw you typing 😅 I was just wondering what the body looks like and if there is a mistake
😅1
@Tom Ireland
@Armand - It looks like you might need to specify that there could be conflicts for tables with constraints.

I've not done bulk updates but I think you need to specify about merging duplicates.

Looking at the API reference in Supabase (bash against the table list for my app), you might need to pass along an additional header: "Prefer: resolution=merge-duplicates"

Don't quote me on that but that should handle existing updates in bulk and insert new records for new ones if using upsert. 🤞
Armand
1 year ago
Yes! That works! I had seen that in the Supabase docs, but I wasn't sure how to use that in the Toddle API interface (and also I wasn't sure it was relevant).

Thanks! (@Mighty you too) 🙏

PS: for anyone finding this in the future and not sure how it should look in the Toddle API interface: see image
👌1
💪1
🙌1
🙏1
Mighty
1 year ago
Do you still need the upsert header?
@Mighty
Do you still need the upsert header?
Armand
1 year ago
let me try without
@Mighty
Do you still need the upsert header?
Armand
1 year ago
No, it is not needed.
Armand
1 year ago
@Max I'm actually updating/saving the order of my items in Supabase, based on your excellent explainer (changing data) video for the drag and drop package
@Armand
@Max I'm actually updating/saving the order of my items in Supabase, based on your excellent explainer (changing data) video for the drag and drop package
Max
1 year ago
Nice 💪🏼😬
@Max
I don't know the answer, so I stopped typing when I saw you typing 😅 I was just wondering what the body looks like and if there is a mistake
Tom Ireland
1 year ago
I had wondered the same as it contained id but that looked to be okay for bulk updates - makes sense as you need an identifier.
@Tom Ireland
I had wondered the same as it contained id but that looked to be okay for bulk updates - makes sense as you need an identifier.
Armand
1 year ago
Not sure, if it's relevant (or interesting), but the body was just an array of objects. In fact the very same objects that I got from that database, but with an adjustment to order field/column.

For context:
1. I have a repeating div that gets it's data from a supabase table
2. Using the Drag and Drop package I then change the order of the items
3. I update/send back the same data but with adjusted order field
@Armand
Not sure, if it's relevant (or interesting), but the body was just an array of objects. In fact the very same objects that I got from that database, but with an adjustment to order field/column.

For context:
1. I have a repeating div that gets it's data from a supabase table
2. Using the Drag and Drop package I then change the order of the items
3. I update/send back the same data but with adjusted order field
Max
1 year ago
Makes sense. I'd probably strip all the info from the array that has not changed. Could lead to overrides if multiple people work on the same items
💯1
@Max
Makes sense. I'd probably strip all the info from the array that has not changed. Could lead to overrides if multiple people work on the same items
Armand
1 year ago
Yes, that's the next step. (coming from Bubble and pretty much a non-coder) I am new to Toddle and working with Supabase, so my first priority was to get it working at all.
💪2
@Max
Makes sense. I'd probably strip all the info from the array that has not changed. Could lead to overrides if multiple people work on the same items
Tom Ireland
1 year ago
Yeah, I imagine if you're just changing sort order or something like that, you'd just need id and sortorder (or whatever the column is called).
@Armand
Yes, that's the next step. (coming from Bubble and pretty much a non-coder) I am new to Toddle and working with Supabase, so my first priority was to get it working at all.
Tom Ireland
1 year ago
Fair play! Nothing like jumping in the deep end eh? It's good because you get to learn how the database actually operates without the additional layer of abstraction and terminology with Bubble.
@Tom Ireland
Fair play! Nothing like jumping in the deep end eh? It's good because you get to learn how the database actually operates without the additional layer of abstraction and terminology with Bubble.
Armand
1 year ago
Yes! Indeed 🙂

Updating multiple records in Supabase

Armand

Mighty

Mighty

Armand

Mighty

Tod

Armand

Tom Ireland

Tom Ireland

Tom Ireland

Max

Armand

Mighty

Armand

Armand

Armand

Max

Tom Ireland

Armand

Max

Armand

Tom Ireland

Tom Ireland

Armand