Skip to main content

Cum se face paginare pe tabelele din Windows Azure

Daca lucram cu tabelele din Windows Azure o sa avem nevoie sa facem paginare. Default nu avem nici un mecanism de paginare, dar acesta este usor de implementat.
In postul anterior am descris modul prin care se pot obtine mai mult de 1000 de entitati dintr-un tabel. Pe baza mecanismului prezentat anterior putem sa parcurgem datele din tabel in format paginat.
Trebuie sa ne folosim de metoda Take din LINQ, care din fericire este suportata si de LINQ folosit pentru tabelele din Windows Azure( nu trebuie sa uitam ca doar o parte din LINQ este implementat pentru Windows Azure in acest moment). Apeland metoda Take putem sa obtinem doar o parte din entitati care ne sunt returnate de catre query.
Folosindu-ne de token-urile nextPartitionToken si nextRowToken putem sa luam urmatoarele x elemente incepand de pe o anumita pozitie.
Mai jos gasiti o implementare minimala a unui mecanism de paginare.
    public class Pagination<TItem>
where TItem : class
{
private const string NoValue = "novalue";

private string _nextPartitionToken;
private string _nextRowToken;
private DataServiceQuery<TItem> _dataServiceQuery;
private List<TItem> _items;
private int _pageSize;

/// <summary>
/// TRUE when another page exist.
/// </summary>
public bool HasNextPage { get { return _nextPartitionToken != NoValue && !string.IsNullOrEmpty(_nextPartitionToken); } }

/// <summary>
/// Gets all the items of the current page.
/// </summary>
public List<TItem> Items { get { return _items; } }

/// <summary>
/// The base contructor.
/// </summary>
/// <param name="dataServiceQuery">The query that is executed on Azure tables.</param>
/// <param name="pageSize">The size of the page.</param>
public Pagination(DataServiceQuery<TItem> dataServiceQuery, int pageSize)
{
_nextPartitionToken = NoValue;
_pageSize = pageSize;
_dataServiceQuery = dataServiceQuery.Take(_pageSize);
}

/// <summary>
/// Load the next page.
/// </summary>
public void NextPage()
{
if(string.IsNullOrEmpty(_nextPartitionToken))
{
return;
}

if (_nextPartitionToken!=NoValue)
{
_dataServiceQuery.AddQueryOption("NextPartitionKey", _nextPartitionToken);
_dataServiceQuery.AddQueryOption("NextRowKey", _nextRowToken);
}

//Get the result.
var result = _dataServiceQuery.Execute();
_items = result.ToList();

//Get tokens for the next page.
QueryOperationResponse queryOperationResponse = (QueryOperationResponse)result;
queryOperationResponse.Headers.TryGetValue("x-ms-continuation-NextPartitionKey", out _nextPartitionToken);
queryOperationResponse.Headers.TryGetValue("x-ms-continuation-NextRowKey", out _nextRowToken);
}
}
Ceea ce lipseste este calcularea numarului total de pagini. Pentru a putea face acest lucru este nevoie sa executam un query care sa returneze numarul total de entitati de pe un anumit tabel.
Pentru ca utilizatorul sa aiba optiunea de a putea accesa orice pagina este nevoie ca in constructor sa executam cate un query pentru fiecare pagina in parte si sa salvam token-urile.

Comments

Popular posts from this blog

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

Can User Technical Profile Influence AI Architecture Decisions?

In the last few days, I ran a small experiment on Devin/Windsurf/Cascade, BMAD, and LLM-based architecture decisions. The initial concern was simple: if an AI coding assistant knows something about the user, for example, that the user is a Java developer or a .NET developer, can this information influence the architecture and technology stack that the AI will propose? This question is important because many companies are starting to use AI tools not only for coding but also for product discovery, architecture, documentation, and technical decision-making. If the AI is influenced by the developer's personal profile, the result may not be fully neutral. It may look like a business or architecture decision, but in reality, it may be partially shaped by the context of the person using the tool. The test was done using BMAD with Devin/Windsurf/Cascade. The scenario was a unified field service operations platform. The task was to let BMAD refine the product, define the architecture and s...

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see...