Postgres: define a default value for CAST failures?

前端 未结 2 1096
感动是毒
感动是毒 2020-12-14 01:44

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\'         


        
2条回答
  •  囚心锁ツ
    2020-12-14 01:57

    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.

提交回复
热议问题