Query around Primary Key in Appian My SQL Database

Hi komalc,

The constraints occur in the following cases:
Databases can enforce constraints on column values that are not enforced by Appian on CDT field values.

For example, a database may require a column value to be "not null", but the field in Appian can be empty. Be aware of these differences when designing your data stores.

Use the attribute nillable="true" to prevent columns in your data store from enforcing a "non-null" constraint.


You can create additional column to save combination values of (Value 1) and (value 2) Make that additional column as PK in your CDT.
From DB side Additional Column should be Unique Key, PK is (value 1 and value 2)

For more info , please have a look on docs.appian.com/.../Database_Schema_Best_Practices.html

Thanks,
ravalik

Hi ravalik

I am aware of the design practice!!
But I am asking this question out of curiosity as I feel this is a limitation that we can have only one column as primary key in CDT be it an additional column which is a combination of two columns or a column in itself.

Also any idea about in which scenario do I get "Unique Key Constraint violated error".

Hi ravalik

I am aware of the design practice!!
But I am asking this question out of curiosity as I feel this is a limitation that we can have only one column as primary key in CDT be it an additional column which is a combination of two columns or a column in itself.

Also any idea about in which scenario do I get "Unique Key Constraint violated error".