Request a Demo
Home   >   mailing lists

On enforcing default column value, AKA "Bloody nulls" - Mailing list pgsql-general

From Wiwwo Staff
Subject On enforcing default column value, AKA "Bloody nulls"
Date
Msg-id CAD1W9HW=PZMZMN7GmPWVUW8BSnvzCYJn=W8nmRXqTaUntSaTdg@mail.gmail.com
Whole thread Raw
Responses Re: On enforcing default column value, AKA "Bloody nulls"
List pgsql-general
Tree view
Hi all!
In a scenario like this:

> =# create table tab1(text1 text default 'from table');
>  
> =# create procedure ins_tab1(p_text1 text default 'from proc') language sql as
> -# $$
> $# insert into tab1(text1) values (p_text1);
> $# $$;
>
> =# call ins_tab1 (null);
>
> =#  select * from tab1 ;
>  text1
> --------
>  [nUlL]

Is there a way (apart from triggers) to force at least one of the default values?

Thanks!


pgsql-general by date:

Previous
From: Tim Gerber
Date:
Subject: Re: Data Out of Sync with Physical Streaming Replication
Next
From: hubert depesz lubaczewski
Date:
Subject: Re: On enforcing default column value, AKA "Bloody nulls"