Tsirkin Evgeny wrote:
> 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)
>> );
>>
>
>
>
No, you should lock the table.
