Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UNEXPECTED BEHAVIOR 'move' method #193

Open
flowtyone opened this issue Jan 24, 2024 · 0 comments
Open

UNEXPECTED BEHAVIOR 'move' method #193

flowtyone opened this issue Jan 24, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@flowtyone
Copy link

Bug report

Describe the bug

When using the 'move' method in javascript storage SDK e.g:

await client.from('bucket_name').move("file_prev_name.ext", "file_new_name.ext");

The moved file's created_at timestamp changes to the current time.

To Reproduce

  1. Create a bucket on supabase
  2. Create a folder and upload a file to it.
  3. Make a request to list the folder using the 'list' method
  4. Observe the 'created_at' date of the uploaded file
  5. Use the javascript sdk as shown above to move the file to another folder.
  6. List the new folder contents, and observe the changed 'created_at' date

Expected behavior

'created_at' timestamp should remain identical to when the file was created, as it would on a normal file explorer.

Additional context

We've moved a large amount of files from one folder to another and this issue has severely impaired our service. We rely on the 'created_at' timestamp to sort files on our product and serve them in a chronological order.

@flowtyone flowtyone added the bug Something isn't working label Jan 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant