| From: | Richard Huxton <dev(at)archonet(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Check constraints on non-immutable keys |
| Date: | 2010-06-30 17:17:50 |
| Message-ID: | 4C2B7C3E.8090107@archonet.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 30/06/10 18:11, Magnus Hagander wrote:
> On Wed, Jun 30, 2010 at 18:33, Richard Huxton<dev(at)archonet(dot)com> wrote:
>>
>> IMHO The real solution would be something that could strip/rewrite the
>> constraint on restore rather than trying to prevent people being stupid
>> though. People *will* just tag their functions as immutable to get them to
>> work.
>
> Are you sure? The people most likely to "just tag their functions as
> immutable", are the same ones most unlikely to know *how to do that*.
> At least for what I think is the majority case - which is calling
> builtin functions.
People just cut and paste this stuff from ancient blog entries.
Understanding is not necessary. Hell, I do it sometimes if I'm dealing
with something like LDAP where I don't really have a deep knowledge of
the situation.
--
Richard Huxton
Archonet Ltd
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-06-30 17:24:34 | Re: 9.0beta2 - server crash when using HS + SR |
| Previous Message | Tom Lane | 2010-06-30 17:16:15 | Re: Check constraints on non-immutable keys |