Hmm. That maybe. I've yet to sit down and try to fully understand the
relations in the system tables. I simply grep'd for pg_attribute and
added a check for "and attisdropped = 'f'".
In each case, I did attempt to run the modified queries to ensure they
still executed and compared the resulting output against the unmodified
queries, however, it doesn't mean I groked what it was really trying to
do.
If you do find corrections to be made, please let me know as I'd love to
know where, what, and why I messed up so I can learn from my mistakes.
Seems the only system tables ERD I have, I find rather hard to
read...guess that will be on my list of items to do today...find a good
ERD of the system tables.
Greg
On Wed, 2002-08-07 at 23:00, Christopher Kings-Lynne wrote:
> Hi Greg,
>
> You should be submitting all these patches to the pgsql-patches mailing
> list...
>
> I will look at your attisdropped patch a bit more carefully as I think some
> of the exclusions you've put in aren't necessary...
>
> Chris
>
> > -----Original Message-----
> > From: pgsql-hackers-owner@postgresql.org
> > [mailto:pgsql-hackers-owner@postgresql.org]On Behalf Of Greg Copeland
> > Sent: Thursday, 8 August 2002 11:50 AM
> > To: PostgresSQL Hackers Mailing List
> > Subject: [HACKERS] Another python patch -- minor
> >
> >
> > This fixes some text as well as enforces the use of "drop table cascade"
> > since we moved from an implicate to explicate implementation.
> >
> > Please find attached the func.py patch.
> >
> > Sorry these are not all one single patch. I really hadn't planned on
> > doing all this...especially not tonight. ;)
> >
> > Greg Copeland
> >
> >
> >
> >
>
