Selective Export in a backwards way?

[SwizzleStack]

Since we currently don't have a selective export, but we do have a selective purge, could I make a copy of the my whole database (using pgdump I'm assuming, dump & restore), then selectively purge what I don't want. So in a roundabout way, it would be kind of like a selective export (and then having those files imported into a new db)? I

[kraada]

Yes, that would do it.

If you feel comfortable at the command line, though, see this thread to get you started.

[SwizzleStack]

Much simpler! Thanks

(is simpler a word? more simple? whatever)

[kraada]

Yes, it is a word, and you're welcome.

Not everyone feels comfortable with the command line, so it's not easier for some -- but I'm glad it works well for you

[SwizzleStack]

I'm like most. If there's a gui that I can be lazy--point, click, & drag, I'll probably use it, but you gotta do what you gotta do! In fact, I've been trying to learn some Ruby on Rails as it seems a really powerful and overall, pretty intuitive way to work with databases (among other things).

[kraada]

I've never tried Ruby on Rails personally; I learned Python back in the day and PHP when it was useful . . . I've heard plenty about Ruby on Rails though and maybe one of these days I'll look into it

(For the record, the "average person" has never heard of Ruby on Rails, I assure you.)

[gspeers]

Yes, that would do it.

If you feel comfortable at the command line, though, see this thread to get you started.

When I use the command line approach - am I doing this through PT3 or am I doing directly to Postgres database?

[kraada]

Directly through the PostgreSQL database; there isn't an interface for selective export in PT3 yet so that's the only way to manage it.