Search Postgresql Archives

Re: null constraints and defaults

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Jun 29, 2005 at 01:46:46PM -0700, elein wrote:

[reformatted]

> 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.

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

Yes; if you want the default value, use DEFAULT instead of NULL.  If it
didn't work that way, how would you insert a NULL in the column?

-- 
Alvaro Herrera (<alvherre[a]surnet.cl>)
"Aprende a avergonzarte más ante ti que ante los demás" (Demócrito)

---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo@xxxxxxxxxxxxxx

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux