Re: Deprecating RULES
От | Robert Haas |
---|---|
Тема | Re: Deprecating RULES |
Дата | |
Msg-id | CA+TgmoZxDN7tN+8HtmXDztmL43Wne383JB2VP4wU9oXd0fxE9A@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Deprecating RULES (Andrew Dunstan <andrew@dunslane.net>) |
Ответы |
Re: Deprecating RULES
Re: Deprecating RULES |
Список | pgsql-hackers |
On Fri, Oct 19, 2012 at 10:29 AM, Andrew Dunstan <andrew@dunslane.net> wrote: > As you can see, in the case of rewrite it takes us back 7 1/2 years. I know > this is a *very* rough measure, but it still tends to indicate to me that > the maintenance burden isn't terribly high. That's a pretty neat one-liner. However... in my view, the real cost of rules is that they are hard to support as we add new features to SQL. I believe we already decided to punt on making them work with CTEs... and maybe one other case? I don't really remember the details any more, but presumably this will come up again with MERGE, and perhaps other cases... -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: