Re: ERROR: duplicate key violates unique constraint "client_alerts_PK" - Mailing list pgadmin-support

From Laurent Yaish
Subject Re: ERROR: duplicate key violates unique constraint "client_alerts_PK"
Date
Msg-id c7e3acb10709122311m3294cb6dr9f1b25aef01f2791@mail.gmail.com
Whole thread Raw
In response to Re: ERROR: duplicate key violates unique constraint "client_alerts_PK"  (Guillaume Lelarge <guillaume@lelarge.info>)
List pgadmin-support
my bad... I missed the post about the default value..


On 9/12/07, Guillaume Lelarge <guillaume@lelarge.info> wrote:
> Laurent Yaish a écrit :
> > Hi Rob,
> >
> > In your insert, do not explicitly specify a value for the primary key,
> > instead use NEXTVAL('client_alerts_seq') which will return the next
> > valid value and increment the sequence.
> >
> > i.e:
> >  insert into clients_alerts (id, client_id, alert_message,
> > alert_complete, date, staff_id)
> > values(NEXTVAL('client_alerts_seq'),'39','This is some alert
> > text','0','2007-05-04 12:42:05','14');
> >
>
> Or, better, he doesn't have to put a value for it as it is already the
> default value for this column :
>
> insert into clients_alerts (client_id, alert_message, alert_complete,
> date, staff_id)
> values('39','This is some alert text','0','2007-05-04 12:42:05','14');
>
> Regards.
>
>
> --
> Guillaume.
>


pgadmin-support by date:

Previous
From: Guillaume Lelarge
Date:
Subject: Re: ERROR: duplicate key violates unique constraint "client_alerts_PK"
Next
From: Charlie Clark
Date:
Subject: Re: Porting from MySQL to postgreSQL. Question RE: Sequence Dependencies