Why you NEED to be using Database Branching!

Рет қаралды 4,916

Supabase

Күн бұрын

Пікірлер: 17

@dombicile4539 29 күн бұрын

You made a very dry subject *super* interesting. Thank you!

@ADHDOCD Ай бұрын

More step by step workflow videos like these for multi-tenant Authorization as well! This makes so much sense now in terms of creating a local vs prod project. Thanks!

@nikhiljay 5 ай бұрын

"Branching is an early access only feature, which must not be used in a production setting."

@francescoimpellizzeri1345 5 ай бұрын

I hope branching will be prod-ready soon! Such a game-changer

@luisandrade1291 5 ай бұрын

Dumb question: so the seed file only runs if it’s not the main branch?

@soilstress 2 ай бұрын

I feel like the cuts cause information to be conveyed incorrectly. 4:28 - CC:`Because RLS blocks everything by default. Secure. But just for the select action.`. Which I hope is not true. I think/hope the [But] sentence is in reference to your specific policy which was maybe just a bad cut in the video???

@akash-kumar737 5 ай бұрын

Supabase is backed for startups.

@rtorcato 5 ай бұрын

does the supabase editor create migrations too? It would be cool if it would add the migrations to a project's repo as a commit.

@funkdefied1 5 ай бұрын

You can use the CLI to diff you DB state against the DB state described in the migration and automatically create a new migration to match them.

@1youngtai 5 ай бұрын

@@funkdefied1 how?

@littlehobbyshop 5 ай бұрын

@@1youngtai Make whatever changes you want in your local supabase instance in the browser UI then run 'npx supabase db pull' it will check for differences between what's in the database now and what's in your migrations. Then it will automatically create a "remote_schema" migration in your project codebase.

@JonathanSummersMuir 5 ай бұрын

@rtorcato > does the supabase editor create migrations too? It would be cool if it would add the migrations to a project's repo as a commit. That's exactly how we thought it could work in the long term.