heavy use of CHECK constraints).
I am unsure wether it is right to send such an uncalled-for patch, but
seeing as this is such a simple thing that can be quite useful (large
volumes of data), I thought it could be useful.
(apply with patch -p0 from the root distro directory)
Cheers
- Jorge Pere
Tom Lane wrote:
Jorge Pereira <[EMAIL PROTECTED]> writes:
... decided to add a couple little variables to control disabling constraints and triggers.
I'm not of the opinion that we actually want any such thing, as it's a
blatant violation of the fundamental concept of data
Christopher Kings-Lynne wrote:
Yes, agreed. I think we decided that super-user-only could disable
trigger on a global basis. I prevent folks from mucking with the system
tables to do it.
It should be a per-table thing:
ALTER TABLE blah [ DISABLE | ENABLE ] [ALL | FOREIGN KEY ] TRIGGERS;
Doing it
for patch, but
seeing as this is such a simple thing that can be quite useful (large
volumes of data), I thought it could be useful.
(apply with patch -p0 from the root distro directory)
Cheers
- Jorge Pereira
*** src/backend/utils/misc/guc.c.orig 2004-05-19 18:52:08.718580424 +0100
--
