Re: Foreign key modification - Mailing list pgadmin-hackers

From Dave Page
Subject Re: Foreign key modification
Date
Msg-id AA30E7BCCA5C1D4E88A231900F8325C00B29@dogbert.vale-housing.co.uk
Whole thread Raw
In response to Foreign key modification  (Jean-Michel POURE <jmpoure@axitrad.com>)
List pgadmin-hackers

> -----Original Message-----
> From: Jean-Michel POURE [mailto:jmpoure@axitrad.com]
> Sent: 27 September 2001 09:08
> To: pgadmin-hackers@postgresql.org
> Subject: Re: [pgadmin-hackers] Foreign key modification
>
>
>
> >Can't you pick an easier one to start with?!?! Foreign Keys are
> >probably the most complex bit of pgSchema...
> >
> >In the simplest terms, pgSchema will need Remove & Add methods in
> >ForeignKeys.cls. These will drop/re-create the three
> triggers that make
> >up the Foreign Key (I assume there is nothing more to an fkey, I've
> >certainly never found anything).
> >
> >If you wish to edit an fkey, you will need to make the relevant
> >property of pgForeignKey.cls read/write and add the code to the
> >Property Let to drop & recreate the relevant trigger in the required
> >way.
> >
> >I would take a look at how ForeignKeys.cls analyses the existing
> >triggers to figure out what the triggers look like and how to best
> >modify them.
> >
> >Regards, Dave.
>
> Hello Dave,
>
> Ok, I though pgSchema already had these features.
> I will have a look at this Remove & Add methods in ForeignKeys.cls.

No, it only (currently) has these methods for objects that can be directly
added or removed with simple SQL. The idea was that we would then make
simple properties Read/Write as we figured out ways to do so, and add
Add/Remove meothods for the more complex things such as ForeignKeys.

/D

pgadmin-hackers by date:

Previous
From: Jean-Michel POURE
Date:
Subject: Re: Foreign key modification
Next
From: Dave Page
Date:
Subject: Re: UNICODE information