| From: | Tim Smith <randomdev4(at)gmail(dot)com> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | Andrew Sullivan <ajs(at)crankycanuck(dot)ca>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Delete rule does not prevent truncate |
| Date: | 2015-07-24 09:24:55 |
| Message-ID: | CA+HuS5E4JEYuP9eYDdFjZSngne-+goKDrDHRz7UMMo4RNhRdfw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
>
> Just in case it has not been made obvious yet, rules are silently
> deprecated. They still exist because views depend on them, but it is
> generally considered best practices to not use them outside that realm.
Well, the manual doesn't seem to reflect that fact.
If that's how the developers feel about rules, i.e they can't be
bothered to make any changes to the rules code any more, no matter how
minor (e.g. this TRUNCATE issue), then you should explicitly state in
the manual that they are depreciated, and stop making stupid
statements like "so if many rows are affected in one statement, a rule
issuing one extra command is likely to be faster than a trigger" that
encourage people to use rules !
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tim Smith | 2015-07-24 09:27:23 | Re: Delete rule does not prevent truncate |
| Previous Message | 林士博 | 2015-07-24 08:55:22 | Re: Re: The fastest way to update thousands of rows in moderately sized table |