Declarative schemas structure/architecture/workflow, tips?
New to supabase and got some broader questions regarding project structure.
- Is it worth the hassle to use the declarative schema functionality? There seems to be limitations with all the diff tools offered which would seem to make it a question of time before something goes wrong.
- Is there a reasonably way to combine using the dashboard and declarative schemas?
supabase db dumpdoes give you the changes you've made in the dashboard but it's in a quite unwieldy format. Is there a better workflow? - I've been programming for various platforms and languages for 15+ years but during all this time I've somehow avoided interfacing directly with SQL. Intuitively it makes sense to me that everything is defined in code for overview and portability. Should I throw this notion out the window? Due to the stateful nature of SQL/postgres there might not be as much value to that approach long term?
- Any tips on reading or videos on architecture or workflows with supabase for a large(r) scale projects? ? I feel I'm quite past the entry level tutorials but haven't really found any good intermediate/expert resources that deals with overall architecture or workflows. Any tips?
