1
Feature Request: Add upsert / overwrite support to storage.move()
Source: supabase/supabase#48566 · opened by @KiddoV
It would be useful if storage.move() supported overwriting the destination file, similar to upload().
Current behavior:
If avatar.jpg already exists, the move fails with a duplicate error. The current workaround is:
Proposed API:
or
This would make move() consistent with upload(), reduce API calls, and simplify common file replacement workflows.
Current behavior:
If avatar.jpg already exists, the move fails with a duplicate error. The current workaround is:
Proposed API:
or
This would make move() consistent with upload(), reduce API calls, and simplify common file replacement workflows.
No pledges yet. Be the first to back this.
Comments
Similar requests
Add upsert option to client API to move an existing file
1 vote · 0 comments
Add Storage Adapter For Chrome.Local.Storage Api
3 votes · 0 comments
copy file wiht upsert as well
1 vote · 0 comments
Add Storage Backups in Sync with Database Backups
4 votes · 0 comments
# Proposal: Virtual Storage Columns (Seamless DB-to-Storage Mapping)
1 vote · 0 comments
No comments yet.