Re: Duplicate data even with primary keys enabled

Поиск
Список
Период
Сортировка
От Teju Jakkidi vlogs
Тема Re: Duplicate data even with primary keys enabled
Дата
Msg-id CAKA2XvaFawqTiRtnYKEz84x4A9rDcY2vDCY2SbkS3e2cNKxLng@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Duplicate data even with primary keys enabled  (Holger Jakobs <holger@jakobs.com>)
Ответы Re: Duplicate data even with primary keys enabled  (Scott Ribe <scott_ribe@elevated-dev.com>)
Re: Duplicate data even with primary keys enabled  (Holger Jakobs <holger@jakobs.com>)
Re: Duplicate data even with primary keys enabled  (Marco DE BOOIJ <marco.maillist@debooy.eu>)
Re: Duplicate data even with primary keys enabled  (Marco DE BOOIJ <marco.developer@debooy.eu>)
Re: Duplicate data even with primary keys enabled  (Samed YILDIRIM <samed@reddoc.net>)
Список pgsql-admin
Hello Jakobs,

I have provided the sample create table and inserts that we are observing. 

CREATE TABLE IF NOT EXISTS "TEST"
(
    "COL1" character varying(9) COLLATE pg_catalog."default" NOT NULL,
    "COL2" character varying(30) COLLATE pg_catalog."default" NOT NULL,
    "COL3" character varying(30) COLLATE pg_catalog."default" NOT NULL,
    "COL4" numeric(10,0) NOT NULL,
    "COL5" character varying(12) COLLATE pg_catalog."default" NOT NULL,
    "COL6" character varying(12) COLLATE pg_catalog."default" NOT NULL,
    CONSTRAINT test_pk PRIMARY KEY ("COL1", "COL2", "COL3")
)

CREATE UNIQUE INDEX IF NOT EXISTS "TEST_UNIQUE"
    ON "TEST" USING btree
    ("COL1" COLLATE pg_catalog."default" ASC NULLS LAST, "COL2" COLLATE pg_catalog."default" ASC NULLS LAST, "COL3" COLLATE pg_catalog."default" ASC NULLS LAST);

CREATE INDEX IF NOT EXISTS "TEST_INDEX"
    ON "TEST" USING btree
    ("COL1" COLLATE pg_catalog."default" ASC NULLS LAST, "COL3" COLLATE pg_catalog."default" ASC NULLS LAST);

Also, the values that we are seeing is as below:

COL1COL2COL3COL4COL5COL6
13456765425ABC1234
13456765425ABC1234
29872897650FGT1234
36547786597JHL8790

We already defined COL1, COL2, COL3 as primary keys, but still as you see above in the table output, the first 2 rows has exactly same combination for those 3 rows.

Thanks,
Teja.


On Fri, Oct 28, 2022 at 11:41 AM Holger Jakobs <holger@jakobs.com> wrote:

Am 28.10.22 um 20:27 schrieb Teja Jakkidi:
> Hi YILDIRIM,
>
> Thanks for your response.
>
> We have a composite primary key on 3columns. We are noticing multiple
> rows with same values in the 3pk columns which should not happen as
> primary constraint is defined on them.
> Also, none of the columns are null.
>
> Regards,
> Teja. J.
>
Unless you don't post your CREATE TABLE command plus some INSERT command
which lead to the described behavior, we won't be able to track the problem.


--
Holger Jakobs, Bergisch Gladbach, Tel. +49-178-9759012

В списке pgsql-admin по дате отправления:

Предыдущее
От: Ron
Дата:
Сообщение: Re: Duplicate data even with primary keys enabled
Следующее
От: Scott Ribe
Дата:
Сообщение: Re: Duplicate data even with primary keys enabled