From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Paulsen <robert@paulsenonline.net>
Cc: pgsql-sql@postgresql.org
Subject: Re: ERROR: null value in column "id" violates not-null constraint
Date: Sat, 10 Oct 2009 16:16:30 -0400
Message-ID: <20765.1255205790@sss.pgh.pa.us> (raw)
In-Reply-To: <200910101405.26853.robert@paulsenonline.net>
References: <200910101056.24051.robert@paulsenonline.net>
<17323.1255200405@sss.pgh.pa.us>
<200910101400.47182.robert@paulsenonline.net>
<200910101405.26853.robert@paulsenonline.net>
Robert Paulsen <robert@paulsenonline.net> writes:
> On Saturday 10 October 2009 2:00 pm, Robert Paulsen wrote:
>> So no default for id. What should it be?
>> default nextval('vault_id_seq')
> Should have tried that before posting last message -- it worked. Thanks!
So the next question is just what happened and whether you're missing
anything else from the original database state ...
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, robert@paulsenonline.net
Subject: Re: ERROR: null value in column "id" violates not-null constraint
In-Reply-To: <20765.1255205790@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox