Jan Wieck wrote: > On 09/14/2014 02:25 PM, Pavel Stehule wrote: > >a) Isn't possible handle a assertion exception anywhere .. it enforce > >ROLLBACK in 100% > > > >b) Assertions should be disabled globally .. I am not sure, it it is a > >good idea, but I can understand so some tests based on queries to data > >can be performance issue. > > > >Important question is a relation assertations and exceptions. Is it only > >shortcut for exception or some different? > > 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 -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
