I don't have a table called objects

but i have storage

could that be it?

Hm, that was weird. I deleted all of the images I uploaded with that user and now I was able to delete the user.

That's got to be an issue that was created somehow by my policies

Hi! I just want to make sure I'm getting this right, correct me if I'm wrong 😄 - Supabase as of now provides a DB with authentication integrated. - If we want to run serverless functions, we need to look elsewhere (like AWS Lambda). - It's possible to self host since this is open source.

My questions are: - Should I wait for Supabase functions or go with some other service? - If another service, which do you recommend? - Other services charge based on compute time of functions. Will DB operations, etc that happen in Supabase happen at the same speed regardless of the provider (say Lambda vs Supabase functions)? - Supabase can be self hosted - is there some migration plan where you can move all data from the hosted to a self-hosted instance?

Check out Vercel, it has serverless functions and integrates with supabase really easily

Anyone using Supabase Python client?

Hello any reason why I am facing this?

I'm trying to update all records in a table to zero out all balances, but I am getting an error not enough input using the python client. I'm trying:

data = supabase.table("inventory").update({"balance" : "0"}).execute()

Response

{'data': {'message': 'Error in $: not enough input'}, 'status_code': 400}

Also, is there a way to do an update where you add X to the existing value without first querying for the current value?

how do i have basic data in a table when a user is created? for example i want the user to have a few "posts" made in their DB / tables when they are created. so basically seeding the database for each user so they start out with the same post.

You can use a trigger on insert on users table that triggers a function that inserts some data in the posts table

Triggers are still not recommended for production right?

Truth be told, I'm not sure why 'Not production ready' tag is shown on the dashboard, since both postgres triggers and postgres functions have been integral to postgres for a very long time

Writing triggers in the SQL editor is safe, the interface for the functions and the triggers is not production ready I think

Any idea why I can't do an update() with Python client?

Can you look in Postgres logs for more info?

How do I do that?

Hi everyone - following up on an issue from last night. When trying to delete a user from the dashboard, I received a fk error. I had deleted all tables with constraints. But the error persisted. A user mentioned the error was on the objects table, so that pointed me to the storage I had set up. Deleting all of the images in a bucket that I uploaded with the user allowed me to delete the user. I'd like to remove this restriction, but I'm not sure how, or why it exists in the first place.

The docs really need work

There's an 'Edit this page' link at the bottom of every page. Constructive contributions and improvements are always appreciated

Documentation is really hard to get perfect, doubly so when the product is new. I'd like to start writing some tutorials for getting up on running on Medium.

But end users shouldn’t struggle with basics

I can’t even figure out how to get update() to work, this is bread and butter of dbs.

What's the issue with update?

My updates are working, so I might be able to help.

hey!