Database schema relations undefined after restoring from backup
See original GitHub issueI’m not 100% sure this is the problem but it seems to be this way.
In my nodejs app, I’ve connected to the supabase postgres db with the credentials given and ran a simple query
SELECT * FROM products
This worked being connected directly to the db with credentials, throughout my development, until I had to restore to a previous backup of my db. Now when I run this query I get this error:
error: relation "products" does not exist
I can run the same query inside the SQL editor on the supabase web client, and I can also run a supabase.from('products').select('*')
just fine as well, but I cannot get any query to work from connecting directly to the db.
This problem happened immediately after restoring from backup.
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Undefined Function when using Database Backup
Ive been using this code to backup my database. ... started (and every after 100 command cycle): if ($st_counter%100 == 0 || $st_counter ......
Read more >[CI] `review_specs_{gke,eks}` failing: "NoMethodError ... - GitLab
It looks like the backup restore is aborting earlier and leaving the database in a bad state because the input prompt isn't being...
Read more >DB2 Redirected Restore NW AS ABAP - SAP Community
Hi,. a system copy with backup/restore allows you to change the connect user but not the database schema. So you need to use...
Read more >Database Engine events and errors - SQL Server
ls" database may have bulk logged changes that have not been backed up. The last log backup on the principal must be restored...
Read more >Error undefined index while upgrading M 2.2.5 > M 2.3.1
The problem is that the SchemaBuilder.php is attempting to look up a table that does not exist in the current database.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
No mistakes on your side, it was a small bug on ours in the restoration process. Sorry about that. There is already a solution to it and a fix should be on its way in the next few days.
I’ll leave this open for now until the fix goes live. Till then, if you are performing any more restores, just ping here so that we can manually fix the last step for you.
Thanks!
Hey @alienzz! So we’ve pushed the changes recently so the bug should be squished. You should now be able to restore your project without that issue. I will be closing this. Do just re-open it if your restorations are still running into trouble.
As for the other issue, if it does persist, feel free to open up another issue on it.
Thanks! 😄