From: | Tsirkin Evgeny <tsurkin(at)mail(dot)jct(dot)ac(dot)il> |
---|---|
To: | Andrei Bintintan <klodoma(at)ar-sd(dot)net> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: duplicates |
Date: | 2004-09-06 09:19:59 |
Message-ID: | Pine.LNX.4.58.0409061211580.20694@p-roman.jct.ac.il |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
yes i understand that i can create a primary key/unique etc...
however my question is if i have to understand if and why
the i got duplicate rows inserted.
so here is the picture:
an application is deleting rows and inserting right after that
new ones some of which are the same as the old one,and i am getting
duplicates !Don't transaction should prevent this by not letting
insert ot do something in case the delete did not succeed?
Another option is that i have to clients deleting and then inserting the
same thing into table ,but again should not transaction prevent duplicates
in that case ?
> Use something like this:
>
> CREATE TABLE schedule (
> id serial PRIMARY KEY,
> studentid decimal(9),
> groupid decimal(10),
> maslulsignid decimal(7),
> tfusot varchar(29)
> );
>
--
Evgeny.
From | Date | Subject | |
---|---|---|---|
Next Message | Kostis Mentzelos | 2004-09-06 09:40:55 | Re: duplicates |
Previous Message | Andrei Bintintan | 2004-09-06 08:31:12 | Re: duplicates |