I want to manage my database items like I manage my code. I get a hierarchical folder structure of items with support for goToDefinition and findReferences, and when I update my code I can run something that generates the diff migration. That way I can see historical context of what has changed and when, rather than looking through migration files grepping for the fields or function names of interest.
The migration log ends up being your changelog, except that it's not a simple diff (create or replace function with the whole definition of the function rather than the diff).
Internally it would materialize it all into a schema which could not only be used for things like go to def, but also for diffing against another schema - either a previous build, or your live db, and subsequently emitted as a migration. It was magical, but flew under the radar, and these days any individual stuck working with SQL Server deserves many condolences.
We use it internally to create folder-like structure representation of our database schema.
https://github.com/gajus/pg-dump-parser?tab=readme-ov-file#r...
Very handy when reviewing changes in version control, etc.
AGPL https://github.com/pgschema/pgschema/blob/97f4bf5c00fd10add5...
MIT https://github.com/pgschema/pgschema/blob/53313057201931b2e8...
Whatever the fuck this is, that ain't community that's "I made up a licence how hard can it be": https://github.com/pgschema/pgschema/blob/6f5ce89cc1ac12f4a6...
