Why do column name set as PropertyName_1 in the database when the PropertyName property is optimized?
Why do column name set as PropertyName_1 in the database when the PropertyName property is optimized? Why not the column name same as property name?
***Updated by moderator: Lochan to add Categories***
Accepted Solution
Pegasystems
IN
It is possible that the same property name might exist (in the class hierarchy) at the top level and at the embedded page. Thus we put _1 for the embedded page levels so that if the top level is optimized, the column name matches the property name.
Updated: 29 Nov 2016 3:09 EST
Pegasystems Inc.
IN
Have you checked your database. Is there already any column with the same name ?
Pegasystems Inc.
IN
Usually this is the format in which name is generated if you are optimizing property in embedded page.
E.x. .Customer.Name : If you optimize .Name property, a new column with Name_1 will be created.
Let us know if this is what you are doing .
Hawaii Medical Service Association
US
question: why Name_1 why not Name? just like the property Name? I got the point it is like this but I am curious why Pega does that.
Accepted Solution
Pegasystems
IN
It is possible that the same property name might exist (in the class hierarchy) at the top level and at the embedded page. Thus we put _1 for the embedded page levels so that if the top level is optimized, the column name matches the property name.
JPMC
IN
If there are multiple single pages having same property name, say for example Customer.Name, Product.Name, Organization.Name , then on optimizing PRPC will create Name_1, Name_2, Name_3 columns in DB. So how do internally PRPC maps these columns to respective Embedded properties?