I have created a data class (concrete) with option: Does Not Belong to a class group and saved it. Generally this class will be mapped to pr_other table. I am using Pega 7.3 PE. I noticed that for each data class, a table is created in the data schema. Is this a design change in Pega 7.3? Is there any specfic reason for doing so?
I understand the high availablity , but the article is not related to my ask. My question is why do we need to create a table for a data class if it is not required.
eg: I want to have a address data class say: myco-fw-data-address, I see a table getting created in data schema. I do not need a table for address class, just want to use it as a data class which holds properties. In lower versions it is mapped to pr_other table. If developer need to map to a table he will do it explicitly. In 7.3 table is created automatically.
If you can throw more details on creation of a table for every data class helps in achieving high availablity. May be I can give a thought.
Posted: 6 years ago
Posted: 17 Jul 2017 16:16 EDT
Pankaj Rawal (rawap)
Fellow Software Architect, App Authoring