On 19 June 2012 22:07, Tom Lane <tgl@xxxxxxxxxxxxx> wrote: > Rafal Pietrak <rafal@xxxxxxxxxxxxxxxxxx> writes: >> The point is, that SQL syntax errors are so obviusly different from >> execution errors, that noting this distinction should not raise any >> ambiguity. > > I beg to disagree. Typos can manifest themselves as execution errors > just as well as syntax errors. The arguments for the current behaviour are clear and rational. I see no challenge possible on that basis. However, PostgreSQL is one of the only databases to behave in this way. This causes some database applications to have subtle problems when we migrate/port them to work with us. Some, though few, programs actually rely on run-time errors in order to execute correctly. I don't condone or encourage that but I do recognise that there is substantial legacy code out there, and much of that needs to run on multiple DBMS. So it would be useful to have a non-default option of statement-level abort for those cases, as an ease of use feature. -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
