>>>>> "Ingo" == Ingo van Lil <inguin@xxxxxx> 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> row in a certain table. And whenever a new line was inserted into that Ingo> table the view should automatically be extended by one column. This seems wrong, with the same spidey sense tingling that triggered (ugh :) yesterday when I said "sending mail from the database is wrong". Your tables shouldn't change during the execution of your application. If they must, you are probably pushing things that belong "above SQL" (like middleware) and forcing SQL to do them, with all the appropriate trouble that results from that. In general, if it looks difficult to do with PostgreSQL, you're probably heading the wrong direction for good database design. -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 <merlyn@xxxxxxxxxxxxxx> <URL:http://www.stonehenge.com/merlyn/> Perl/Unix/security consulting, Technical writing, Comedy, etc. etc. See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
