Received: from localhost (unknown [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 370A12E00C8 for ; Thu, 29 Nov 2007 10:16:32 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 08234-09 for ; Thu, 29 Nov 2007 10:16:22 -0400 (AST) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.182]) by postgresql.org (Postfix) with ESMTP id 416272E397A for ; Thu, 29 Nov 2007 10:16:28 -0400 (AST) Received: by py-out-1112.google.com with SMTP id u77so4070456pyb for ; Thu, 29 Nov 2007 06:16:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; bh=zkbAlOYJV5m1U7sY4RNYGzoZw3zNVWH9KCYiEAoOUA0=; b=Wh1KYLOazo7EN8txTRcLfeSBYcWw+3uijNWL1t0qociGB7iUGAwpQvmU8W/pgw9D5x5dr3lTZcFxpFhSx042kX6BSPUZrAPgoMQUDgRbSvy8RwSvy9cdY27x/cnsgcHhO66euLE2aZH7u7OsJhSbTRdc4/WqPUxMmkWjuy1WUnk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; b=rWooSnGtzqx65rpPMVmYVxd79Gv9LbktqqA/HKG7sbnEmuGX/sJ5CJkV84J+zkJ505uuL/dId9DmWtVnleyoiXQOAECgj7mHmtuDSwtww5mVdFs25N0M7JrirSbx0kI5+evcbaD/bmzeGg6xXlckIoPeuR2TFKFhXtmuyInFyVA= Received: by 10.65.23.7 with SMTP id a7mr1773028qbj.1196345786516; Thu, 29 Nov 2007 06:16:26 -0800 (PST) Received: from ?192.168.1.4? ( [68.197.152.70]) by mx.google.com with ESMTPS id f12sm3768863qba.2007.11.29.06.16.24 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 29 Nov 2007 06:16:25 -0800 (PST) Message-ID: <474EC9CE.9090609@gmail.com> Date: Thu, 29 Nov 2007 09:16:46 -0500 From: Stephen Cook User-Agent: Thunderbird 1.5.0.13 (Windows/20070809) MIME-Version: 1.0 To: pgsql-sql@postgresql.org Subject: Re: statement-level trigger sample out there? References: <20071129130159.110470@gmx.net> <162867790711290548t2a050d59ta77595c2b05d59ce@mail.gmail.com> In-Reply-To: <162867790711290548t2a050d59ta77595c2b05d59ce@mail.gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200711/154 X-Sequence-Number: 29682 I am curious (coming from a MS SQL Server background, I just started playing with PostgreSQL recently). What type of situation would warrant a statement-level trigger that can't access the old and new values? Without that access, isn't the only information you get is the fact that an operation occurred on the table? Or am I missing something? -- Stephen Pavel Stehule wrote: > Hello > > You cannot to access to values in statement trigger. Postgres doesn't > support it. > > Regards > Pavel Stehule > > On 29/11/2007, Christian Kindler wrote: >> Hi >> >> Can anyone provide me a simple example of a statement-level trigger? Problem is I do not know how to access the old.*, new.* values. >> >> Thanks >> Chris >> -- >> GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS. >> Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail >> >> ---------------------------(end of broadcast)--------------------------- >> TIP 1: if posting/reading through Usenet, please send an appropriate >> subscribe-nomail command to majordomo@postgresql.org so that your >> message can get through to the mailing list cleanly >> > > ---------------------------(end of broadcast)--------------------------- > TIP 1: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to majordomo@postgresql.org so that your > message can get through to the mailing list cleanly >