-
Notifications
You must be signed in to change notification settings - Fork 292
Closed
Description
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
When I try to start local development I get a 500 DatabaseError
and the project fails to start.
To Reproduce
Update the supabase cli
to version 2.31.4
and restart local development by:
- executing
supabase stop --no-backup
on the project terminal - erasing docker images and volumes
- running
supabase start
- the console outputs the following error:
Error status 500: {"statusCode":"500","code":"DatabaseError","error":"DatabaseError","message":"select * from ((select \"id\", \"name\", \"type\", \"public\", \"owner\", \"created_at\", \"updated_at\", \"file_size_limit\", \"allowed_mime_types\" from \"buckets\") union all (select \"id\", \"id\" as \"name\", \"type\", null as \"public\", null as \"owner\", \"created_at\", \"updated_at\", null as \"file_size_limit\", null as \"allowed_mime_types\" from \"buckets_analytics\")) as \"all_buckets\" - column \"type\" does not exist"}
Expected behavior
The local development server should start with no problem, but it does not.
System information
- OS: macOS 15.5
- Supabase-cli: 2.31.4
- Node.js: 24.4.0
Additional context
It looks like the issue is the new Iceberg Analytics Bucket
that is not available yet to execute locally.
LeonSchallenberg, davidbond17, lws803, leandrocabranes, schmingle and 18 more
Metadata
Metadata
Assignees
Labels
No labels