Migrating from Supabase

Re:Migrating from Supabase by dingledork69 on Friday May 19, 2023 @04:32PM (#36006536)

I don't use supabase, but am a big postgres fan:

> that stuff in unmaintainable

Wrong. Version your functions and use something like liquibase to apply migrations.

[ Parent | on HN ]

Re:Migrating from Supabase by ilrwbwrkhv on Friday May 19, 2023 @04:35PM (#36006573)

And handwrite xml? No thanks. Again, if I wanted to do any of this management myself, I wouldn't be using a PaaS.

[ Parent | on HN ]

Re:Migrating from Supabase by dingledork69 on Friday May 19, 2023 @08:04PM (#36008169)

You don't have to use the xml format if you don't want to. Not sure why you wouldn't want to, since the xsd enables autocompletion in your IDE which makes it the most practical format of all.

Anyway, YAML and SQL format are a thing

https://docs.liquibase.com/concepts/changelogs/yaml-format.h...

https://docs.liquibase.com/concepts/changelogs/sql-format.ht...

[ Parent | on HN ]

Re:Migrating from Supabase by tianzhou on Saturday May 20, 2023 @01:27AM (#36009594)

Or Bytebase if you want a more sophisticated GitLab like experience

[ Parent | on HN ]

Re:Migrating from Supabase by koromak on Friday May 19, 2023 @05:35PM (#36007116)

Way less friendly than writing code IMO

[ Parent | on HN ]

Re:Migrating from Supabase by dingledork69 on Friday May 19, 2023 @08:06PM (#36008176)

Far, far more performant though for filtering millions of rows

[ Parent | on HN ]

Re:Migrating from Supabase by flagrant_taco on Saturday May 20, 2023 @12:44AM (#36009439)

Developer friendly matters early on, performance and security friendly matters at scale

[ Parent | on HN ]