After updating my db, I had a profile-pictures bucket, and it ALL uploads were erased. This isn't a huge issue for now, but wondering if anyone has any tips for updating.
Supabase gives you the tools, documentation, and community that makes managing databases, authentication, and backend infrastructure a lot less overwhelming.
What do you mean my updating db? Is this on Supabase hosted? Just doing an infrastructure upgrade would not change the storage.objects table (metadata) or the actual s3 file data.
I would certainly update frequently when in development and before launching production. Then I would only update if I needed to for some bug or over some longer time spam just to keep current. But normally I would have a dev instance at least to test first.
I use MCP with Cursor, but monitor every change. I definitely need to start making changes in dev before production db. I haven't figured how to do that yet.
I'll do an upgrade to the current release just to make sure there is not a bug. Are your other tables' data there? It also implies your storage.buckets table is fine if the bucket is still there. Seems odd to only have one table wiped.
Then that makes no sense from an infra point of view. It would not know one bucket from another in storage.objects table. They are all intermixed. So something would have had to delete particular rows by bucket id.
Did you do a DB restore from back up at some point to before these files existed? Would have been in past 7 days and you would need to be Pro or do you own backups for that. That could update the storage.objects table back to before those files existed.