Excerpts from Ross J. Reedstrom's message of mar may 31 14:02:04 -0400 2011:
> Follows from one of the practical maxims of databases: "The data is > always dirty" Being able to have the constraints enforced at least for > new data allows you to at least fence the bad data, and have a shot at > fixing it all. Right now, you may be forced into running with > constraints effectively 'off', depending on the app to get new data > right, while attempting to catch up. And the app probably put the bad > data in there in the first place. One of the thankless, important but > seemingly never urgent tasks. Interesting point of view. I have to admit that I didn't realize I was allowing that, even though I have wished for it in the past myself. -- Álvaro Herrera <alvhe...@commandprompt.com> The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
