• State Not Answered
  • Replies 28 replies
  • Subscribers 7 subscribers
  • Views 19805 views
  • Users 0 members are here
Related Discussions
Home » Discussions » General

Questions about Querying Data from an RDBMS

harshav

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
  • 0
    Certified Lead Developer
    @sharshs - A few comments:

    re 1. Do you have metrics to back this up? What you're implying is that a query rule totally ignores the pagingInfo that you give it; I don't believe this is the case.
    re 2. When you say "query entity has good performance than query rule" are you saying that query entity is ALWAYS faster? I don't believe this is correct. A comparison of a query rule returning all 100 fields of an entity and a query entity returning only 5 of those fields will, of course, show a performance increase, but I'd suggest that the difference is negligible for similar numbers of fields.
    re 4. This simply isn't true; adding an input to a query rule and filtering by that input will limit the results. The performance benefit of query entity is shown when selecting subsets of columns for a given data entity.

    I'd be interested in some input from Appian on this; the recommendation of "appian recommends use of query entity over query rule" seems far too broad and doesn't take into account the extra effort an maintenance of query entity over a query rule.
Reply
  • 0
    Certified Lead Developer
    @sharshs - A few comments:

    re 1. Do you have metrics to back this up? What you're implying is that a query rule totally ignores the pagingInfo that you give it; I don't believe this is the case.
    re 2. When you say "query entity has good performance than query rule" are you saying that query entity is ALWAYS faster? I don't believe this is correct. A comparison of a query rule returning all 100 fields of an entity and a query entity returning only 5 of those fields will, of course, show a performance increase, but I'd suggest that the difference is negligible for similar numbers of fields.
    re 4. This simply isn't true; adding an input to a query rule and filtering by that input will limit the results. The performance benefit of query entity is shown when selecting subsets of columns for a given data entity.

    I'd be interested in some input from Appian on this; the recommendation of "appian recommends use of query entity over query rule" seems far too broad and doesn't take into account the extra effort an maintenance of query entity over a query rule.
Children
No Data
© 2024 Appian. All rights reserved.
We want to hear from you! Submit a review on Gartner or G2.