Blog

All Blog Posts | Next Post | Previous Post

My Top 10 Aurelius Features - #5 LINQ Expressions and Paging

Monday, January 30, 2017

Most examples and quick-start tutorials about ORM frameworks explain how to insert, update and retrieve single entities in the database. But not many of them go further and show how to perform a query in the database. Maybe because that's something that the developer will only need after many data is inserted, and it's something that is only heavily needed when the application development is at a more advanced stage. However, it's a very important feature, and that's why "LINQ Expressions and Paging" is my #5 feature of My Top 10 Aurelius Features.

The reason for that is because you can really query your entities in a object-oriented way. It's not some SQL-like string you build, or SQL WHERE statement that you simply inject. It's really about querying object properties, comparing their values in Pascal (not in database), and using Pascal syntax to build the queries. Take a look at this example:

  MyCustomers := Manager.Find<TCustomer>
    .Where(
      (
         (Linq['Birthday'] > EncodeDate(1981, 10, 10))
         and (Linq['Birthday'] < EncodeDate(1986, 2, 2))
      )
      or ((Linq['Sex'] = tsFemale) or Linq['Sex'].IsNull)
      or Linq['Name'].Contains('Walker')
      or Linq['Status']._In([TCustomerStatus.Active, TCustomerStatus.Prospect)
    )
    .OrderBy('Name')
  .List;

That's an example of filtering by Birthday property using logical operators "and", "or", how you can use parenthesis and have Delphi give you compile errors if expression is wrongly constructed. And of course you have extra expressions like "Contains", "In", etc.. All in Pascal.

Finally, a small feature of LINQ filtering that I enjoy a lot: paging. It's very simple to use and very handy:

  MyCustomers := Manager.Find<TCustomer>
    .Take(10).Skip(50)
    .OrderBy('Name')
    .List;

The code above in theory should bring all customers, but will only bring 10 customers, skipping the first 50 in the specified order. This is great for bringing a long list but in parts, page by page. And of course you can use it with any criteria you specify, like the complex one illustrated above in this post.

To see in details how LINQ expressions and paging works, watch the video above, and if you want to get notified about upcoming videos, subscribe to our YouTube channel!

Wagner Landgraf

This blog post has received 2 comments.

1. Wednesday, December 4, 2024 at 1:18:38 AM

Hello,

Following the kind of pagination definitions explained in this link :

https://medium.com/@PradipBhusnar/sql-for-pagination-queries-memory-and-performance-567af4913b50

What kind of pagination does Aurelius uses?, Indexed pagination or KeySet pagination?

I do the question because the Indexed pagination does have degradation in response times over large datasets while KeySet pagination keep the response times consistent.

Thank you.

Conde Cantero Manuel Alonso

2. Wednesday, December 4, 2024 at 11:46:16 PM

Aurelius uses whatever the database support, might be LIMIT/OFFSET, or TAKE, or ROW OVER. I don''t think the article is very "scientific". It doesn''t even mention the RDBMS used, and I think it affects. So at first sight the article is just a "guess" from the author. In any case, you can use the timestamp technique yourself, since it depends on your app. For more detailed discussion, please use our Support Center.