Skip site navigation (1) Skip section navigation (2)

Re: Deprecating RULES

From: "Greg Sabino Mullane" <greg(at)turnstep(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Deprecating RULES
Date: 2012-10-12 02:58:18
Message-ID: 9569b30050c7712ba08556124d507688@biglumber.com (view raw or flat)
Thread:
Lists: pgsql-hackers
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160


Tom and Simon wrote:
>> If you want to get rid of rules, build the
>> replacement; don't just try to be a pain in the ass to users.

> Supporting broken and non-standard features *is* a pain in the ass to
> users, since they are sometimes persuaded to use them and then regret
> it. Or if they do, hit later problems.

Broken? That's a strong word. Tricky perhaps. Best avoided by novices, yes. 
But broken? Do they not work exactly as described in the fine manual?
FWIW, I still see them a lot in the wild.

> Anyway, lets start with a discussion of what rules give us 
> that SQL standard features do not?

Even if the answer is nothing, if we do not implement the SQL standard 
feature yet (exhibit A: updateable views), it's a moot point unless 
the goal is to spur development of those features just so we can 
deprecate rules.

- -- 
Greg Sabino Mullane greg(at)turnstep(dot)com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201210112251
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iEYEAREDAAYFAlB3hx8ACgkQvJuQZxSWSshhwQCfdtKc7R2i0kz7eDUTXtik93k3
KyEAoK0dQVZsfcAD3OlHYDVhWMjst8QZ
=xY2L
-----END PGP SIGNATURE-----




In response to

pgsql-hackers by date

Next:From: Alvaro HerreraDate: 2012-10-12 03:44:23
Subject: Re: Deprecating RULES
Previous:From: Andrew DunstanDate: 2012-10-12 00:52:27
Subject: Re: Deprecating RULES

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group