On 9/16/14 12:01 AM, Alvaro Herrera wrote: > Jan Wieck wrote: >> I think that most data integrity issues can be handled by a well >> designed database schema that uses UNIQUE, NOT NULL, REFERENCES and >> CHECK constraints. Assertions are usually found inside of complex >> code constructs to check values of local variables. I don't think it >> is even a good idea to implement assertions that can query arbitrary >> data. > > Actually Peter Eisentraut posted a patch for SQL assertions: > http://www.postgresql.org/message-id/1384486216.5008.17.ca...@vanquo.pezone.net
SQL assertions are just a kind of CHECK constraint, so fully Jan-compliant. ;-) I don't mind PL/pgSQL having an "assert" statement like many programming languages, but I find a lot of the proposed details dubious. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
