On 01/13/2014 05:10 PM, Jim Nasby wrote: > On 1/13/14, 7:06 PM, Josh Berkus wrote: >> Regularly? No. But I've seen it, especially as part of a "does this >> query return any rows?" test. That's not the best way to test that, but >> that doesn't stop a lot of people doing it. > > Right, and I certainly don't want to force anyone to rewrite all their > code. But I'd certainly like a safer default so people don't mistakenly > go the "multiple rows is OK" route without doing so very intentionally.
The problem is that if you change the default, you're creating an unexpected barrier to upgrading. I just don't think that it's worth doing so in order to meet some standard of code neatness, especially in plpgsql, the unwanted bastard child of SQL and ADA. For people who want to enable this in order to prevent stupid query bugs from creeping into their plpgsql, that's great, let's have an easy option to turn on. But it's hard enough to get people to upgrade as it is. If we're going to add an upgrade landmine, it better be for something really important. -- 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
