Repository wrapper for Azure Table Storage
See the version list below for details.
Install-Package TableStorage.Abstractions -Version 1.0.5
dotnet add package TableStorage.Abstractions --version 1.0.5
<PackageReference Include="TableStorage.Abstractions" Version="1.0.5" />
paket add TableStorage.Abstractions --version 1.0.5
#r "nuget: TableStorage.Abstractions, 1.0.5"
// Install TableStorage.Abstractions as a Cake Addin #addin nuget:?package=TableStorage.Abstractions&version=1.0.5 // Install TableStorage.Abstractions as a Cake Tool #tool nuget:?package=TableStorage.Abstractions&version=1.0.5
This version includes a fix for an issue where inserting more than 100 entries for a given partitionkey caused an error.
see the Azure Table Storage documentation https://docs.microsoft.com/en-us/dotnet/api/microsoft.windowsazure.storage.table.tablebatchoperation?view=azurestorage-8.1.3
"A batch operation may contain up to 100 individual table operations, with the requirement that each operation entity must have same partition key. A batch with a retrieve operation cannot contain any other operations. Note that the total payload of a batch operation is limited to 4MB."
NuGet packages (2)
Showing the top 2 NuGet packages that depend on TableStorage.Abstractions:
A repository wrapper for Azure Table Storage that uses POCOs (Plain Old CLR Objects) instead of objects that implemeent ITableEntity. The Azure Storage SDK requires that objects that it works with to implement the ITableEntity interface. This puts us into one of two places that are often not desirable: You implement the ITableEntity interace, or inherit from TableEntity. This is easy, but now you've got a leaky abstraction, as well as properties that won't make much sense in your domain (e.g. instead of a UserId, you've now got a RowKey, of the wrong type), or you have fields that are out of place, like ETag and Timestamp. You create DTOs to save to ship data back and forth from the domain to Table Storage. This is a common style, but often is overkill, especially if we're just looking for a simple abstraction on top of Azure Table Storage. This simple library seeks to take care of the mapping for us, so that you can continue to write your domain objects as POCOs, while still being able to leverage the Azure Storage SDK. The library will convert simple properties to fields in Azure Table Storage. Complex types will serialize as json.
An implementation of a trie-like data structure using Azure Table Storage to enable type-ahead style searching. Targets netcoreapp2.1, netstandard2.0 and net461.
This package is not used by any popular GitHub repositories.