Re: removing duplicated constraints
| От | Stephan Szabo | 
|---|---|
| Тема | Re: removing duplicated constraints | 
| Дата | |
| Msg-id | 20020302110754.K52221-100000@megazone23.bigpanda.com обсуждение исходный текст  | 
		
| Ответ на | Re: removing duplicated constraints ("Dan Langille" <dan@langille.org>) | 
| Ответы | 
                	
            		Re: removing duplicated constraints
            		
            		 | 
		
| Список | pgsql-admin | 
On Sat, 2 Mar 2002, Dan Langille wrote:
> On 2 Mar 2002 at 10:19, Dan Langille wrote:
>
> > CREATE CONSTRAINT TRIGGER "<unnamed>" AFTER INSERT OR UPDATE ON "ports"
> > FROM "categories" NOT DEFERRABLE INITIALLY IMMEDIATE FOR EACH ROW EXECUTE
> > PROCEDURE "RI_FKey_check_ins" ('<unnamed>', 'ports', 'categories',
> > 'UNSPECIFIED', 'category_id', 'id');
> >
> > CREATE CONSTRAINT TRIGGER "<unnamed>" AFTER INSERT OR UPDATE ON "ports"
> > FROM "categories" NOT DEFERRABLE INITIALLY IMMEDIATE FOR EACH ROW EXECUTE
> > PROCEDURE "RI_FKey_check_ins" ('<unnamed>', 'ports', 'categories',
> > 'UNSPECIFIED', 'category_id', 'id');
>
> How is an unnamed trigger deleted?  During a dump, I can find information
> such as this:
The "<unnamed>" is the constraint name given.  It also gets a trigger name
(see system table pg_trigger) which you can use with DROP TRIGGER
(although in the case of the fk constraint triggers you need to double
quote the name).
		
	В списке pgsql-admin по дате отправления: