Hello,

I work as a dba and get requests from developers to create tables which we often review and sometimes change for better design and/or implementation.

One of the developers recently sent a request to create a table such as the following ;

table_name:t1_relation

Column_names:
c1_master_id_pk (foreign key to t1_master table)
c1_attribute
c1_value

primary key all 3 columns.

They explained that the data in all these columns are all non nullable and that they are all needed to uniquely identify a record.

having all the columns of a table as a primary key didn't look very right to me and so
I suggested we create a surrogate key and make the 3 columns unique with not null constraints on all of them. they initially said yes then came back and said to change it to be how they requested initially.

I'm messaging to ask if this is proper database design and what would be the ideal way to implement this?