Question
Rabobank Netherlands
NL
Last activity: 18 Jul 2017 10:45 EDT
Best practice to expose data tables?
Is it a good practice to expose data table so that if we apply any obj method on it , then instead of searching BLOB column of PR_OTHER , it will search at exposed column of a specific table.
I am populating value from a data table using dynamic select, should i expose it or not from performance point of view .
***Updated by moderator: Lochan to close post***
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Accepted Solution
Pegasystems
IN
It is more a matter of the use case. If the read are very infrequent, and can be cached in, let's say a data page, then maybe it's okay to leave it in the BLOB. That said, the number of records returned should be low as well.
But Phani is right that mapping to pr_other should be avoided and we do have an alert that highlights this issue when Work- classes are mapped to it - https://pdn.pega.com/performance/understanding-the-pega0041-alert-work-object-written-to-the-pr-other-table
Pegasystems Inc.
IN
yes. if there is no specific table to be mapped, we should be using 'pr_Data' instead of 'pr_Other'. Otherwise, a specific table with explicit columns is always recommended for better performance.
Accepted Solution
Pegasystems
IN
It is more a matter of the use case. If the read are very infrequent, and can be cached in, let's say a data page, then maybe it's okay to leave it in the BLOB. That said, the number of records returned should be low as well.
But Phani is right that mapping to pr_other should be avoided and we do have an alert that highlights this issue when Work- classes are mapped to it - https://pdn.pega.com/performance/understanding-the-pega0041-alert-work-object-written-to-the-pr-other-table