On 01/13/2014 03:41 PM, Florian Pflug wrote: > It therefor isn't an oversight that SELECT ... INTO allows multiple result > rows > but INSERT/UPDATE/DELETE forbids them, it's been done that way on purpose and > for a reason. We shouldn't be second-guessing ourselves by changing that > later - > not, at least, unless we have a *very* good reason for it. Which, AFAICS, we > don't. > > (And yeah, personally I'd prefer if we'd complain about multiple rows. But > it's > IMHO just too late for that)
I *really* don't want to go through all my old code to find places where I used SELECT ... INTO just to pop off the first row, and ignored the rest. I doubt anyone else does, either. -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
