Re: Why does an ON SELECT rule have to be named "_RETURN"?
From:
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To:
Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>
Cc:
Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>,
Martijn van Oosterhout <kleptog(at)svana(dot)org>,
"pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>,
Peter Eisentraut <peter_e(at)gmx(dot)net>, ken(at)sunward(dot)org
Subject:
Re: Why does an ON SELECT rule have to be named "_RETURN"?
Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> writes:
> This is semi-orthogonal, but I'd hoped that with first-class updatable
> views we might get some method to determine which columns are actually
> updatable, but perhaps this is just wishful thinking?
All of them I should think. I certainly don't see us automatically
creating update rules for any cases where this isn't so.
regards, tom lane
