From: | Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: back-end triggers front-end to update |
Date: | 2005-07-27 10:07:05 |
Message-ID: | 20050727100705.GD2945@merkur.hilbert.loc |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Jul 26, 2005 at 06:25:23PM -0300, Adam O'Toole wrote:
> I am searching for a way to have my postgresql 7.4.7 backend be triggered to
> let the front end know there has been a change to the database. If more then
> one person is connected to the database and person (x) makes a change, I want
> other clients to then be aware of that, and refresh there screen so they are
> not then looking at out of date data.
> Any insight? Thank you so much, have a great day.
GNUmed has a complete Python implementation of what you
describe. We are using triggers and listen/notify as others
suggested. Look at client/pycommon/gmBackendListener.py for
the middleware, then server/sql/gmNotifications.sql for the
schema support, and server/bootstrap/gmNotificationSchemaGenerator.py
for a way to generate the needed triggers at the time of
bootstrapping the database.
http://salaam.homeunix.com/~ncq/gnumed/snapshot/gnumed-latest-snapshot.tgz
Karsten
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
From | Date | Subject | |
---|---|---|---|
Next Message | Walsh, Richard (Richard) | 2005-07-27 11:08:03 | Re: dropping non-existent tables |
Previous Message | Roman Neuhauser | 2005-07-27 09:31:09 | Re: Postgresql with max_connections=4096 |