Bobbie Soedirgo

As mentioned above, you can configure the [setting](https://app.supabase.com/project/_/settings/api) (API settings > Exposed schemas) and set the `schema` property when initializing the client lib. You also need to apply `GRANT`s for...

Am able to resolve the permission error with grants, so closing the issue. ```sql create or replace function public.test_function() returns int as $$ select extensions.levenshtein('a', 'b'); $$ language sql; grant...

Hmm, I'm not sure this warrants a new command. Wouldn't a shell alias or command history + completion do a better job? cc @parrotmac

Got it, thanks for sharing your situation! The CLI should be tearing down resources on error, but I also noticed this sometimes doesn't work, specifically when there is an error...

Closing this as we decided to fix the [underlying issue](https://github.com/supabase/cli/issues/253) instead. `supabase start && supabase stop` is expected to properly tear down existing containers.

Thanks all, seems like this issue is the same as https://github.com/supabase/cli/issues/210#issuecomment-1201213636, which should be fixed by now.

Hey, sorry for the late reply! I actually thought of using go-npm at the start as being able to get started without installation steps is a big DX win (e.g....

I'm not familiar with GitPod, but can you do everything the Docker CLI can do inside it?

Thanks for the suggestion! This is likely going to be a config eventually, e.g.: ```toml [functions.my_function] no_verify_jwt = true ```

Hmm yeah, error reporting could be improved here by also printing which migration file and more context from psql. One litmus test would be: you should know where the error...