Postgres: define a default value for CAST failures?

Question

Is it possible to define a default value that will be returned in case a CAST operation fails?

For example, so that:

SELECT CAST('foo' AS INTEGER) 

Will return a default value instead of throwing an error?

Answer 1

There is no default value for a CAST:

A type cast specifies a conversion from one data type to another. PostgreSQL accepts two equivalent syntaxes for type casts:

CAST ( expression AS type ) expression::type 

There is no room in the syntax for anything other than the expression to be casted and the desired target type.

However, you can do it by hand with a simple function:

create or replace function cast_to_int(text, integer) returns integer as $$ begin     return cast($1 as integer); exception     when invalid_text_representation then         return $2; end; $$ language plpgsql immutable; 

Then you can say things like cast_to_int('pancakes', 0) and get 0.

PostgreSQL also lets you create your own casts so you could do things like this:

create or replace function cast_to_int(text) returns integer as $$ begin     -- Note the double casting to avoid infinite recursion.     return cast($1::varchar as integer); exception     when invalid_text_representation then         return 0; end; $$ language plpgsql immutable;  create cast (text as integer) with function cast_to_int(text); 

Then you could say

select cast('pancakes'::text as integer) 

and get 0 or you could say

select cast(some_text_column as integer) from t 

and get 0 for the some_text_column values that aren't valid integers. If you wanted to cast varchars using this auto-defaulting cast then you'd have to double cast:

select cast(some_varchar::text as integer) from t 

Just because you can do this doesn't make it a good idea. I don't think replacing the standard text to integer cast is the best idea ever. The above approach also requires you to leave the standard varchar to integer cast alone, you could get around that if you wanted to do the whole conversion yourself rather than lazily punting to the built in casting.

NULL handling is left as an (easy) exercise for the reader.

Answer 2

Trap the error as described in documentation and then specify an action to do instead.

Documentation on error trapping for PostgreSQL Snippet included below.

35.7.5. Trapping Errors

By default, any error occurring in a PL/pgSQL function aborts execution of the function, and indeed of the surrounding transaction as well. You can trap errors and recover from them by using a BEGIN block with an EXCEPTION clause. The syntax is an extension of the normal syntax for a BEGIN block:

[ <<label>> ] [ DECLARE     declarations ] BEGIN     statements EXCEPTION     WHEN condition [ OR condition ... ] THEN         handler_statements     [ WHEN condition [ OR condition ... ] THEN           handler_statements       ... ] END; 

If no error occurs, this form of block simply executes all the statements, and then control passes to the next statement after END. But if an error occurs within the statements, further processing of the statements is abandoned, and control passes to the EXCEPTION list. The list is searched for the first condition matching the error that occurred. If a match is found, the corresponding handler_statements are executed, and then control passes to the next statement after END. If no match is found, the error propagates out as though the EXCEPTION clause were not there at all: the error can be caught by an enclosing block with EXCEPTION, or if there is none it aborts processing of the function.