Question
JPMorgan Chase
US
Last activity: 18 Jul 2017 6:02 EDT
Table is created for a data class
Hi
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?
Thanks
Sam
Pegasystems Inc.
IN
Yes, this is a design change going forward in Pega for achieving High availability. You can read more details on below link and let us know if this helps :)
JPMorgan Chase
US
Hi rawap
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.
Thanks
Sam
Pegasystems Inc.
IN
No, it has nothing to do with high availability. Guess, misunderstood your question.
Back to your actual concern.
How are you creating these data classes? Are you using a wizard to create them?
Just the creation of data class should never create and map to a new table automatically even now in Pega 7.3
JPMorgan Chase
US
I am creating a class without using wizard. I have a DBadmin role in my access group. I am able to figureout the issue. I think this is a bug in product.
Check this activity: pzValidateCreateTableForClass. step 1 and step 6.
Steps to reproduce:
1. In access group make sure you have this role: PegaRULES:DatabaseAdministrator
2. Create a data class and it should not belong to class group. Save it.
3. Verify the data schema: two tables will be created one for data class and one for history.
In the above mentioned activity in step one they are checking for db privelege for table creation if true, going ahead for table creation( I think there should be one more condition here)
In step 6, I checked the code high level, there is a issue which pyClassGroupIndicator==NOCLASSGROUP. Still creating table.
Let me know if this is a bug .
Thanks
Sam