Questions about Querying Data from an RDBMS

with Reference to this below URL,
forum.appian.com/.../Querying_Data_From_an_RDBMS.html
There are some doubts out of my interest.
Lets consider a scenario, like we have a view which is having 100k of data and it is trying to fetch the data with pagination with 25 records per page. we are using Query rules and we are in version 7.4
Knowing that pagination is given it will load only 25 records per page but our doubt is since pagination is used in the expression rule of displaying the data in grid,
1.Is Query Rule fetching all the records and showing 25 per page or is it hitting the db for the next 25 records,
2.Is this the same way how Query Entity works or is it different.
3.Knowing that the maximum limit of data for Query rule is 1 MB, is it the same for Query Entity or does this differ.
4.How does the performance of Query rule and Query Entity differ if the working of both are same.
Please Sugges...

OriginalPostID-196692

OriginalPostID-196692

  Discussion posts and replies are publicly visible

Parents
  • 1. Query rule fetches all records in one go and it only shows 25 per page.
    2. Query rule is different than query entity , query entity has good performance than query rule and in query entity you can do things which you cannot do in query rule like query rule does not support OR operator in its filter criteria.
    3. Same for both.
    4.Performance is effected because in query entity you can limit your data selection very well but in query rule you cannot limit your selection e.g if you just want to fetch a single column from your database for particular filter , you can do that in query entity but not in query rule. Plus as i mentioned earlier also appian recommends use of query entity over query rule.
Reply
  • 1. Query rule fetches all records in one go and it only shows 25 per page.
    2. Query rule is different than query entity , query entity has good performance than query rule and in query entity you can do things which you cannot do in query rule like query rule does not support OR operator in its filter criteria.
    3. Same for both.
    4.Performance is effected because in query entity you can limit your data selection very well but in query rule you cannot limit your selection e.g if you just want to fetch a single column from your database for particular filter , you can do that in query entity but not in query rule. Plus as i mentioned earlier also appian recommends use of query entity over query rule.
Children
No Data