Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Discussion

 Jeeva Shanmugavel (JeevaS22)
iNautix Technologies India Private Limited
Applications Developer Trainee
iNautix Technologies India Private Limited
IN
JeevaS22 Member since 2013 2 posts
iNautix Technologies India Private Limited
Posted: Dec 3, 2015
Last activity: Mar 7, 2016
Posted: 3 Dec 2015 14:44 EST
Last activity: 7 Mar 2016 0:13 EST
Closed

Usage of RDB-List method for querying Internal Class Instances

I was going through the Online Help System and under Working with PegaRULES Database, I came across the following:

"You can also use Connect SQL rules to search the database, but this is not recommended except in unusual situations."

I am trying to understand why usage of RDB-List is not recommended over Obj-Browse for filtering out Internal Class Instances. Is it only because Obj-Browse will generate a well-structured query internally or is there some other technical reason? Also can you cite one 'unusual situation' where Obj-Browse method is not usable but RDB-List is? A simple comparison over RDB-List and Obj-Browse methods is appreciated.

Thanks in advance.

Jeev

To see attachments, please log in.
Reporting

Posted: 8 years ago
Posted: 28 Jan 2016 11:53 EST
Mary Swanson (swanm) Manager, Technical Documentation
Pegasystems Inc.
US

You should be able to filter out class instances by using report definitions, so I'd stick with using report definitions. (I'm not sure of the use cases for Connect SQL rules.) 

To see attachments, please log in.

Related content:

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice