X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org
Received: from localhost (unknown [200.46.204.144])
	by svr1.postgresql.org (Postfix) with ESMTP id 1A18C8B9C3C
	for <pgsql-sql-postgresql.org@localhost.postgresql.org>;
	Mon, 14 Feb 2005 20:03:17 +0000 (GMT)
Received: from svr1.postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id 58794-09
	for <pgsql-sql-postgresql.org@localhost.postgresql.org>;
	Mon, 14 Feb 2005 20:03:08 +0000 (GMT)
Received: from boutiquenumerique.com (boutiquenumerique.com [82.67.9.10])
	by svr1.postgresql.org (Postfix) with ESMTP id AC9CE8B9F78
	for <pgsql-sql@postgresql.org>; Mon, 14 Feb 2005 20:03:06 +0000 (GMT)
Received: (qmail 22373 invoked from network); 14 Feb 2005 21:03:37 +0100
Received: from unknown (HELO musicbox) (boutiquenumerique-lists@192.168.0.2)
	by boutiquenumerique.com with SMTP; 14 Feb 2005 21:03:37 +0100
To: =?iso-8859-15?Q?AL=DD_=C7EL=DDK?= <ali@verus.com.tr>,
	pgsql-sql@postgresql.org
Subject: Re: triggers
References: <cuqgst$2adi$1@news.hub.org>
Message-ID: <opsl7d5owoth1vuj@musicbox>
From: PFC <lists@boutiquenumerique.com>
Organization: =?iso-8859-15?Q?La_Boutique_Num=E9rique?=
Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Date: Mon, 14 Feb 2005 21:06:50 +0100
In-Reply-To: <cuqgst$2adi$1@news.hub.org>
User-Agent: Opera M2/7.54u1 (Linux, build 892)
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, hits=0.004 tagged_above=0 required=5 tests=AWL
X-Spam-Level: 
X-Archive-Number: 200502/145
X-Sequence-Number: 20256


> update trigger  working on same table???

	If an UPDATE trigger does an update on its own table, it can trigger  
itself and explode...