| From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> | 
|---|---|
| To: | Laurent Yaish <laurenty(at)gmail(dot)com> | 
| Cc: | Robert Starr <rob(at)surrenderdorothy(dot)com(dot)au>, pgadmin-support(at)postgresql(dot)org | 
| Subject: | Re: ERROR: duplicate key violates unique constraint "client_alerts_PK" | 
| Date: | 2007-09-13 06:05:43 | 
| Message-ID: | 46E8D337.7090201@lelarge.info | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgadmin-support | 
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurent Yaish | 2007-09-13 06:11:12 | Re: ERROR: duplicate key violates unique constraint "client_alerts_PK" | 
| Previous Message | Robert Starr | 2007-09-13 06:01:09 | Re: restoring a backup and maintaining dependencies? |