Han Qiao comments

Results 421 comments of


                                            Han Qiao

Applying migrations returns "cannot insert multiple commands into a prepared statement"

> It seems like the following RLS policy causes the error Thank you for providing this script. Unfortunately I tried to reproduce locally without success. Here's the sql file I...

Applying migrations returns "cannot insert multiple commands into a prepared statement"

I'm able to reproduce the error with your example now. It should be fixed in v1.8.7. Appreciate your help so far.

Add hooks to cli commands

Also related is #160 which asks for pre/post-migration sql files.

`db remote changes` wants to rename a column to every other column

Thanks for informing us of this issue. I will look into adding migra support for remote diff to handle this case.

`db remote changes` wants to rename a column to every other column

We have added `supabase db diff --use-migra --linked` flag to diff against linked project in latest version. Let us know if it works so we can default to use migra...

Sync local postgrest container version with hosted

Hi @Marviel , I'm getting different versions for my hosted project. ```json { "swagger": "2.0", "info": { "description": "standard public schema", "title": "PostgREST API", "version": "9.0.1.20220717 (pre-release) (d2df289)" ``` and...

Generating types with postgis extension lead to file with lint errors.

Thanks for reporting this issue. May I check if you installed postgis in `extensions` schema or created its own `postgis` schema?

"Applying migration" output corrupted

Hello, I will look into making the logs prettier tmr. A temporary workaround is redirect stderr to NUL or $null on PS. ```powershell supabase start 2> $null ```

show migration new help when called without arguments

Closing this in favour of #562

Getting error "relation "pgsodium.key_key_id_seq" does not exist (SQLSTATE 42P01)" when using "db remote commit"

Hello @ARMATAV , `supabase/extensions.sql` is a file that we no longer support in CLI v1 and I suspect it was working for you by accident... Could you and @ZetiMente help...