Some Tables from OOTB Pega 7 are missing primary keys on them
There are some tables in pega 7 ( we are using Pega717/718) which do not have Primary keys defined on them. For example pr_sys_updatescache and pr_index_Info. In some of our client places when trying to upgrade to Pega7 or creating new Pega7 environment the Client Database teams are rejecting creation of such tables with out primary keys. GCS recommended us to post this question here. I am looking for details/info around why these tables deliberately left without a primary key by pega , and are there any plans for pega to add keys to these tables in future. If client insists on standards can we go ahead an create a new column and make it primary key. What are Pega's thoughts around this.
Pegasystems Inc.
US
Both tables exist before Pega 7. pr_sys_updatescache is an internal table used for sync up rules updates cross multi-nodes. There is no need of primary key. pr_index_info is used for previous release in AES. It is already gone. There is no plan to add primary key for updatescache table.
Pegasystems Inc.
IN
Hello everyone, Good Morning!
>>> There are some tables in pega 7 ( we are using Pega717/718) which do not have Primary keys defined on them. For example pr_sys_updatescache and pr_index_Info
| Class Name | Table Name | Class Keys | Ruleset/Version |
|---|---|---|---|
| System-Updates-Cache | pr_sys_updatescache |
pxSystemName pxNodeName pxCreateDateTime |
Pega-RULES: 04-01-01 |
| PegaAESRemote-Interface-IndexData | pr_index_Info | No Keys | PegaAESRemote: 01-01-07 |
>>> In some of our client places when trying to upgrade to Pega7 or creating new Pega7 environment the Client Database teams are rejecting creation of such tables with out primary keys
Hello everyone, Good Morning!
>>> There are some tables in pega 7 ( we are using Pega717/718) which do not have Primary keys defined on them. For example pr_sys_updatescache and pr_index_Info
| Class Name | Table Name | Class Keys | Ruleset/Version |
|---|---|---|---|
| System-Updates-Cache | pr_sys_updatescache |
pxSystemName pxNodeName pxCreateDateTime |
Pega-RULES: 04-01-01 |
| PegaAESRemote-Interface-IndexData | pr_index_Info | No Keys | PegaAESRemote: 01-01-07 |
>>> In some of our client places when trying to upgrade to Pega7 or creating new Pega7 environment the Client Database teams are rejecting creation of such tables with out primary keys
- Gowrishankar Ramasamy - could you please share your thoughts.
>>> I am looking for details/info around why these tables deliberately left without a primary key by pega , and are there any plans for pega to add keys to these tables in future
- please refer to Jie Long comment.
>>> can we go ahead an create a new column and make it primary key
- we can not update the class rule from
- it may even break some of the existing code where we do not have control on pega internal/final rules throwing not null/primary key violation error
>>> thoughts around this
- would extending our own organization specific class with keys to the OOTB classes
- and mapping to cloned version of OOTB database tables make sense/help? or
- writing RDB- methods helps for DB operations...?
- note: RDB methods are DB platform dependent.
Please share your thoughts/comments, Thank you!
psahukaru
Pegasystems Inc.
IN
note:
- keys defined on class rule form as class key
- need not be a primary key....
- but it (the key defined on class rule form) should not be null.
Pegasystems Inc.
IN
- also a table can exist without a primary key but defined with class keys on class rule form which are not null...
Please correct/share your thoughts/comments, Thank you!
psahukaru