> Josh's position that "this should be standard SQL" is nonsense, or > at least he ought to be making that argument to the standards committee > not us.
Huh? When did I say that? > If we want something built-in, maybe providing some prefab plpgsql > functions is the way to go. But we'd have to arrive at a consensus > on what best practice of that form looks like. *Built-in* functions are just as good as extra syntax, as far as I'm concerned. Functions which require installing plpgsql, reading the docs, creating a function, pasting it in, and saving it are NOT as good; they are unlikely to ever be used, except by the people who didn't really need them in the first place. -- Josh Berkus PostgreSQL Experts Inc. www.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
