Thanks to visit codestin.com
Credit goes to github.com

Skip to content

schemas, ordering, complexity. #597

Description

@xpusostomos

I've spent the last few days trying to come up with some kind of a cut down demo I can give to my organisation about how we might use this, maybe something with only one schema, something that excludes a lot of stuff with .pgschemaignore, something that doesn't try and utilize multi-file dumps, and I couldn't do it. There is quite a lot of complexity in our model, and you'll need some time to get it working. I think I'm going to have to back away from using this for a while to give you more time to develop it. I think you need the multi schema. I also think you need a way to automatically exclude things that depend on things in other schemas. Since the program presumably is forming some kind of dependency graph of what depends on what, this ought to be feasible at some point.

Anyway, my gift to you... or maybe my curse is I'm attaching here our entire database schema dump, with all our schemas. I would suggest this is a pretty good test case if you've got all the bases covered. If you can load this, dump it and plan it without intervention, I would love to dip my foot back in the water and get involved, otherwise I might have to back away from it for a while... good luck.

pgdump_all.sql

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions