pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: charpent@bacbuc.dyndns.org
Cc: pgsql-general@postgresql.org
Cc: pgsql-interfaces@postgresql.org
Subject: Re: problem with update rules on a view (ODBC)
Date: Sun, 12 Jan 2003 14:06:00 -0500
Message-ID: <29803.1042398360@sss.pgh.pa.us> (raw)
In-Reply-To: <avsd4d$1i1m$1@news.hub.org>
References: <avsd4d$1i1m$1@news.hub.org>

Emmanuel Charpentier <charpent@bacbuc.dyndns.org> writes:
> I am trying to create a small applications using a PostgreSQL 7.2 database, 
> updated through ODBC from an OpenOffice form.
> ...
> I tried my  rules "by hand" in psql : the update works as advertised in the 
> docs. However, I noticed that updating the *real" table gives a message :
> UPDATE 1
> after updating the table, while updating the view gives the message
> UPDATE 0
> after "updating" the view (i. e. updating the underlying table).

You can control this in 7.3 by adjusting the rule firing order (which
you do by choosing the names you give to the rules); see
http://www.ca.postgresql.org/users-lounge/docs/7.3/postgres/rules-status.html

I am not sure there is any good workaround in 7.2.

			regards, tom lane



view thread (5+ messages)  latest in thread

Message-ID: <29803.1042398360@sss.pgh.pa.us>
Permalink:  ../29803.1042398360@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/29803.1042398360@sss.pgh.pa.us

 · 

reply

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-interfaces@postgresql.org
  Cc: tgl@sss.pgh.pa.us, charpent@bacbuc.dyndns.org, pgsql-general@postgresql.org
  Subject: Re: problem with update rules on a view (ODBC)
  In-Reply-To: <29803.1042398360@sss.pgh.pa.us>

* 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