Dealing with postgres dependencies

[bpeck81]

Edit:

I've deprecated this method and wrote a post of what I prefer to do here #11212

Issues with dependencies:

I've been learning postgres as I build my project in supabase and found myself wanting to really lean into using views and functions. The problem is that postgres punishes you for using them without knowing your column schemas ahead of time. To make a change you have to drop cascade, and in my case, I had 30 indirectly dependent objects I was frequently dropping.

I made some functions to help deal with dependencies and take full advantage of views and functions.

I hope this helps save people some of the pain I went through to create a good workflow!

Here's an example of how to use it:

select * from dep_save('public','viewa'); -- Save dependencies

drop view viewa cascade; -- Drop all of your objects

create or replace viewa as select col1 from viewb; -- Modify your source object

select * from dep_restore(); -- Restore the dependencies

select dep_unsave(); -- Clear the save cache

Repo:
https://github.com/bpeck81/dep_postgres