From: | "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com> |
---|---|
To: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
Cc: | <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: enhancement to pg_dump: supress columns |
Date: | 2005-10-14 12:22:01 |
Message-ID: | 6EE64EF3AB31D5448D0007DD34EEB3417DD5B6@Herge.rcsinc.local |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Christopher wrote:
> A general ability to be able to dump views as if they were tables
would
> be more broadly applicable methinks?
>
> Merlin Moncure wrote:
> > I have a situation where I need to hack pg_dump not to dump columns
with
> > a particular name. If this is of interest to the community I can
spend
> > a little extra effort and work up a patch. I'd be curious to see if
> > anyone else thinks this is worthwhile.
> >
Yes, although that would not solve my particular problem. Since I don't
want to dump a particular column that is present in all tables, using
views would mean creating a lot of views for one purpose :(. Basically,
I have a simulated oid which is superior to the provided oid in all ways
except one, in that the oid allows you to keep it from dumping.
Another example of a column you might not want to dump is
passwords...although that's a fairly weak case. hmm, I might be out in
the wilderness on this one.
Merlin
From | Date | Subject | |
---|---|---|---|
Next Message | C Wegrzyn | 2005-10-14 12:23:34 | Re: [PATCHES] [BUGS] BUG #1962: ECPG and VARCHAR |
Previous Message | Dave Page | 2005-10-14 12:08:07 | Re: Open items |