topic Re: To avoid adding duplicate key entries to table in Application Development and Automation Discussions

To avoid adding duplicate key entries to table

Pavithra_madhu — Mon, 09 Jan 2017 10:40:16 GMT

Hi,

I have created a custom table and there is a field with numc 4. I changed that field to decimal with 2 decimal points. using SE14 i'm going to adjust the table but error occured and stop with error log. then I re enter SE14 and then "unlock table" button clicked and activated my table. After that my table can add duplicate entries to key fields. How to disable adding duplicate entries to key fields of my table??

Re: To avoid adding duplicate key entries to table

Sandra_Rossi — Mon, 09 Jan 2017 11:48:29 GMT

How could it be possible that the database let you add 2 records with same primary key? I can't imagine it could just be a bug! Please give more information about what happens exactly.

Re: To avoid adding duplicate key entries to table

former_member197132 — Mon, 09 Jan 2017 13:50:00 GMT

Hello Prvithra,

Make that field primary key.

Re: To avoid adding duplicate key entries to table

Pavithra_madhu — Tue, 10 Jan 2017 03:14:11 GMT

they are primary key fields.. but it allow duplicate.. I also cann't imagine it.. but it happend. this is an exapmle.. i can add any number of duplicate records with same primary key now..

Re: To avoid adding duplicate key entries to table

Pavithra_madhu — Tue, 10 Jan 2017 03:15:53 GMT

they are primary key fields.. but it allow duplicate.. I also cann't imagine it.. but it happend. this is an exapmle.. i can add any number of duplicate records with same primary key now..

Re: To avoid adding duplicate key entries to table

Sandra_Rossi — Tue, 10 Jan 2017 08:33:40 GMT

You should get the key fields and compare them via the debugger (compare tool).

Moreover, make sure the primary index (named ~0) is still there in the database (SE14, index), and create it if it's not there.

Re: To avoid adding duplicate key entries to table

Sandra_Rossi — Tue, 10 Jan 2017 08:33:59 GMT

make sure the primary index (named ~0) is still there in the database (SE14, index), and create it if it's not