Search Postgresql Archives

Re: Why does an ON SELECT rule have to be named "_RETURN"?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



"Ken Winter" <ken@xxxxxxxxxxx> writes:
> * Why this constraint?  
> * Would anything break if I were allowed to get away with my little trick?  
> * Is there any way to get around the constraint?

The reason why the table is converted to a view is that ancient pg_dump
dumps used to create views in exactly that way (make a table and then
add an ON SELECT rule) and so when we started making a hard distinction
between tables and views, we needed to force the conversion to occur.

The notion of a real table that has an ON SELECT rule seems fairly
broken to me in any case.  I think you should be complaining to the
authors of your client-side tools that they won't do what you want.
It would probably be quite a trivial change to get them to support
data entry forms against views, but changing the backend on this
point won't be an easy sell.

			regards, tom lane


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux