Josh Trutwin wrote:
> Is there a better way to do this? Maybe a stored proc that eats the
> error message?
Well, you can use a plpgsql function with a BEGIN/EXCEPTION/END block to
"eat" the error message. However I'm wondering whether you should be
checking the aggregate argument type(s) as well.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.