From: | Mike Meyer <mwm(at)mired(dot)org> |
---|---|
To: | Christoph Haller <ch(at)rodos(dot)fzk(dot)de> |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: Rule for updating through a view. |
Date: | 2003-03-24 17:31:45 |
Message-ID: | 15999.16641.828710.981313@guru.mired.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
In <3E7F2C01(dot)E012A174(at)rodos(dot)fzk(dot)de>, Christoph Haller <ch(at)rodos(dot)fzk(dot)de> typed:
> Is it this what you've found and can't get to work?
Yes, that was what I found. I was having trouble figuring out how it
*should* work. I think I've got it now - the missing idea was that the
new and old rows contain the *entire* rows, not just what was being
updated. That makes it possible to pull values from them and udpate
entire rows in the table(s) the view joins. At least, that's the way I
believe it should work. My views don't have enough information to
identify a unique row in those tables, so I can't do this safely
anyway.
Thanks,
<mike
--
Mike Meyer <mwm(at)mired(dot)org> http://www.mired.org/consulting.html
Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information.
From | Date | Subject | |
---|---|---|---|
Next Message | Antti Haapala | 2003-03-24 18:36:31 | Re: function with security definer |
Previous Message | Christoph Haller | 2003-03-24 16:02:09 | Re: Rule for updating through a view. |