Without having read the entire thread ...
On 09/01/2014 05:04 AM, Joel Jacobson wrote:
From the top of my head, these are Things I personally would want to
see in plpgsql2:
+ Make UPDATE/INSERT/DELETE throw error if they didnt' modify exactly 1
row, as that's the most common use-case, and provide alternative syntax
to modify multiple or zero rows.
I think this is a completely flawed proposal "by definition". SQL itself
does not make such assumption and as a SET oriented language, never
should. A SET is zero or more tuples. Would you also suggest that the
PostgreSQL backend throw an ERROR if an UPDATE/INSERT/DELETE doesn't
modify exactly 1 row? If not, explain why there should be a difference
between SQL executed from the frontend and SQL executed by a PL/pgSQL
-1 from me.
+ Change all warnings into errors
I suggest being slightly more selective on that one.
Senior Software Engineer
Sent via pgsql-hackers mailing list (email@example.com)
To make changes to your subscription: