On Wed, Dec 28, 2005 at 07:29:28PM +0100, Ingo van Lil wrote:
> Now, if I want to get a list of users that have a certain combination of
> valid status entries (e.g. all users that have paid their annual fee and
> are not banned for some reason), I have to use several subselects:
>
> SELECT person
On 28 Dec 2005, Randal L. Schwartz wrote:
>> Well, in my case the situation is further complicated by the fact that
>> adding a column to the view should be done automatically from a trigger
>> function. I wanted some kind of matrix view that had a column for every
>> row in a certain table. And w
Ingo van Lil wrote:
On 28 Dec 2005, Florian G. Pflug wrote:
I could think of a few situations where extending a view might be
useful, and I'd appreciate to see it supported. I don't see any reason
not to allow it as long as no existing columns are removed or have their
type changed.
Well, some
> "Ingo" == Ingo van Lil <[EMAIL PROTECTED]> writes:
Ingo> Well, in my case the situation is further complicated by the fact that
Ingo> adding a column to the view should be done automatically from a trigger
Ingo> function. I wanted some kind of matrix view that had a column for every
Ingo> ro
On 28 Dec 2005, Florian G. Pflug wrote:
> >I could think of a few situations where extending a view might be
> >useful, and I'd appreciate to see it supported. I don't see any reason
> >not to allow it as long as no existing columns are removed or have their
> >type changed.
>
> Well, some other v
Ingo van Lil wrote:
Hi there,
is there any way to add new columns to a view without dropping and
recreating it (and thus every other view that depends on it)? A friend
of mine came up with a crude hack that involves manipulating the reltype
flag in pg_class so Postgres thinks the view is actualy
