Hi,
does Postgresql 7.1 support triggers on a view actions? I've defined a few but they
doesn't seem to get fired. Problem is I cannot easily set the trigger on the tables
because of permission issues...
Lieven
---(end of broadcast)---
TIP 3:
Tom Lane wrote:
> Lieven Van Acker <[EMAIL PROTECTED]> writes:
> > Well, in fact, -at this point - I don't need setuid, because the
> > function current_adm() has to lookup the effective uid of the calling
> > user. The point is I want to filter the records depe
Tom,
do I have to restore the original rewriteHandler.c? (before the first patch)
Lieven
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
> Okay, the example you sent me off-list turns out to exhibit one bug
> and one not-yet-implemented feature. There is a bug in permissions
> checking for insert/update/delete rules (any references therein to
> NEW or OLD should be checked against the rule owner, not the calling
> user). A patch
Hi Jan and others,
thanks for the answer, this clears up the symptom.
In trying to rewrite the rules, I'm still facing the same problem.
I'll try to simplify the rules and tables (it's emulating the OO concept as
a is the parent and b and c are inherited from a)
CREATE TABLE a (x integer PRIMAR
Hi Andrew,
I'm sorry but I was a but sloppy in typing. The right version is
CREATE TABLE a (x integer PRIMARY KEY,y integer);
CREATE TABLE b (x integer REFERENCES a, z integer, PRIMARY KEY (x,z))
CREATE VIEW ab AS
SELECT a.x, a.y, b.z
FROM a,b
WHERE a.x=b.x;
/* this -insert- seems
