Re: Proof of concept: auto updatable views [Review of Patch] - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Proof of concept: auto updatable views [Review of Patch]
Date
Msg-id 1349919561.30900.4.camel@vanquo.pezone.net
Whole thread Raw
In response to Re: Proof of concept: auto updatable views [Review of Patch]  (Dean Rasheed <dean.a.rasheed@gmail.com>)
Responses Re: Proof of concept: auto updatable views [Review of Patch]  (Dean Rasheed <dean.a.rasheed@gmail.com>)
List pgsql-hackers
Compiler warning needs to be fixed:

rewriteHandler.c: In function 'RewriteQuery':
rewriteHandler.c:2153:29: error: 'view_rte' may be used uninitialized in this function [-Werror=maybe-uninitialized]
rewriteHandler.c:2015:17: note: 'view_rte' was declared here

Duplicate OIDs need to be adjusted:

FATAL:  could not create unique index "pg_proc_oid_index"
DETAIL:  Key (oid)=(3172) is duplicated.

Maybe we should distinguish updatable from insertable in error messages
like this one:

ERROR:  cannot insert into view "foov2"
DETAIL:  Views containing DISTINCT are not updatable.

The SQL standard distinguishes the two, so there could be differences.
I'm not sure what they are right now, though.

This hint could use some refreshing:

HINT:  You need an unconditional ON INSERT DO INSTEAD rule or an INSTEAD OF INSERT trigger.

Maybe something along the lines of

HINT:  To make the view insertable anyway, supply an unconditional ... etc.




pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: change in LOCK behavior
Next
From: Tom Lane
Date:
Subject: Re: [PATCH 8/8] Introduce wal decoding via catalog timetravel