Re: null constraints and defaults

From: elein(at)varlena(dot)com (elein)
To: Matt Miller <mattm(at)epx(dot)com>
Cc: elein <elein(at)varlena(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: null constraints and defaults
Date: 2005-06-29 20:46:46
Message-ID: 20050629204646.GG7997@varlena.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Thanks. I understand that much. I want to know if this
is the intended behaviour.

--elein

On Wed, Jun 29, 2005 at 08:25:09PM +0000, Matt Miller wrote:
> On Wed, 2005-06-29 at 13:04 -0700, elein wrote:
> > default constraint
> > ...
> > elein=# insert into nulldefault values (NULL);
> > ERROR: null value in column "one" violates not-null constraint
>
> I think the idea of a DEFAULT value is to tell the DB what to supply
> only if you omit the column from the insert statement altogether. If
> you deliberately call for a NULL, the DB will try to oblige.
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Stephan Szabo 2005-06-29 20:50:17 Re: null constraints and defaults
Previous Message Charles Swiger 2005-06-29 20:40:52 Re: PostgreSQL's vacuumdb fails to allocate memory for non-root users