Re: Insert problem
От | Jamie Tufnell |
---|---|
Тема | Re: Insert problem |
Дата | |
Msg-id | b0a4f3350803091714n2b89425ev48410eb86451b973@mail.gmail.com обсуждение исходный текст |
Ответ на | Insert problem ("A. R. Van Hook" <hook@lota.us>) |
Список | pgsql-sql |
On 3/9/08, A. R. Van Hook <hook@lota.us> wrote: > The script worked fine untill I tried in on the following entries: > > 1841 | 2 | 9228 : Caty Case : SO:Bra:..... > 1841 | 3 | 9621 : Kelsie Greenlee : PROM..... > > 2072 | 3 | null : Cookie Jared Cook :.......... > 2072 | 4 | null : Cookie Jared Cook :........ > 2072 | 5 | null : Cookie Jared Cook :........ > > insert into schItem (scid, value, iflag, outalts, sidate, istid) > > ERROR: duplicate key violates unique constraint "schitem_pkey" > > table defination > > create sequence schItem_item_seq > create table schItem > (scid int NOT NULL references schedule ON DELETE CASCADE, > item int NOT NULL default nextval('schItem_item_seq'), [snip] It looks like there's already a row where scid=2072 and item=nextval('schItem_item_seq'). Try: SELECT setval('schItem_item_seq', (SELECT max(item)+1 FROM schItem)); And then run your query again. Cheers, J.
В списке pgsql-sql по дате отправления: