From: Enrico Weigelt <weigelt@metux.de>
To: pgsql-sql <pgsql-sql@postgresql.org>
Subject: Re: trigger/rule question
Date: Mon, 2 May 2005 05:31:34 +0200
Message-ID: <20050502033134.GD24546@nibiru.borg.metux.de> (raw)
In-Reply-To: <02767D4600E59A4487233B23AEF5C59922C29D@blrmail1.aus.pervasive.com>
References: <02767D4600E59A4487233B23AEF5C59922C29D@blrmail1.aus.pervasive.com>
* Ramakrishnan Muralidharan <ramakrishnanm@pervasive-postgres.com> wrote:
Hi,
> Going through you mail, I assume that you are updating the mtime
> only after inserting the record.
An "normal" update (=done by an application or user) should also
update the mtime. But there's an replication subsystem, which writes
should go through untouched.
> It is always possible to check the mtime filed value of the inserted
> record and take action based on it in the trigger.
yeah, but how to detect whether the application has explicitly
written it ?
The only chance I currently have in mind is to use some session
dependent data, i.e. username or some persistant storage (could be
easily done ie. w/ plphp) for this decision. The sync subsystem
has to do some "special" login (ie. separate user or setting the
session wide variable) before doing its work.
I would be happier to let a rule do this, so there's not an extra
function per written row. But all my experiments ran into infinite
recoursion trouble.
> Is it possible to send me detail about the trigger?
The trigger isn't existing yet. I'm currently maintaining the mtime
updates within the application, but I wanna get away from that. It
probably would be interesting, if a normal application couldn't
touch the mtime at all.
cu
--
---------------------------------------------------------------------
Enrico Weigelt == metux IT service
phone: +49 36207 519931 www: http://www.metux.de/
fax: +49 36207 519932 email: contact@metux.de
---------------------------------------------------------------------
Realtime Forex/Stock Exchange trading powered by postgresSQL :))
http://www.fxignal.net/
---------------------------------------------------------------------
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: weigelt@metux.de
Subject: Re: trigger/rule question
In-Reply-To: <20050502033134.GD24546@nibiru.borg.metux.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox