Re: pg_get_triggerdef in pg_dump - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject Re: pg_get_triggerdef in pg_dump
Date
Msg-id 14e101c3353a$894101a0$6500a8c0@fhp.internal
Whole thread Raw
In response to pg_get_triggerdef in pg_dump  ("Christopher Kings-Lynne" <chriskl@familyhealth.com.au>)
Responses Re: pg_get_triggerdef in pg_dump  (Andreas Pflug <Andreas.Pflug@web.de>)
List pgsql-hackers
> this arguments are quite academic. 

You what!

> On one side, this could be 
> restricted, thats what pg_depends is good for (this already happens for 
> inherited tables).
> On the other side, how often do you rename columns or tables?

You what!

> On mssql, nobody cares. 

You what!

> If you fool around with names, your views will 
> be broken without warning. pgsql could be better easily.
> I'd really prefer to have full view sources available rather than the 
> gimmick of stable views despite renamed cols/tabs.

Gimmick!  You what!!!!!!




pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: sa_family_t in cygwin compile of cvs
Next
From: "Francisco Figueiredo Jr."
Date:
Subject: Fields float4 don't return any row when selecting a value with a .