Question
Deloitte Touche Tohmatsu India LLP
IN
Last activity: 28 Nov 2024 15:56 EST
Issue with multiple primary keys for a concrete class
We have a concrete class with 2 keys. We have exposed these 2 key columns from Pega data designer. Now while using a data set of this concrete class as a destination in a data flow, if any one of the key is blank, still data is getting saved in the table and there is no database save error.
Do we need to drop the column and readd the column with not null query?
How to resolve this issue?
Pegasystems Inc.
IN
you may need to ensure that the primary key constraints are correctly defined in the database. If the keys are not set to 'NOT NULL', the database will allow blank values to be saved. You can drop the existing key column and re-add it with a 'NOT NULL' constraint to enforce this rule. This will prevent any records from being saved without valid key values. Additionally, ensure that the keys defined in Pega match the primary key columns in the database to avoid any mismatches.
Deloitte Touche Tohmatsu India LLP
IN
@thulg I understand it does not have a not null constraint as of now. But please share the process of readding the column with not null constraint post dropping. We don't have access to DB admin as it is on Pega cloud.
Do we need to raise ticket and with column drop and column add queries with pega support?
Pegasystems Inc.
CA
Yes, please create a CC ticket to configure composite primary keys and define it "NOT NULL" as Thulasi suggested.