If you’re using Azure Table Storage then it’s often more efficent to perform operations such as insert, update, delete in batches rather than making seperate calls for each individual row. There can be up to 100 entities in each batch and each all entities in a batch need to have Read more…
If you have a complex table structure in SQL that you want to map into corresponding classes in your .NET Core project it might be easier to output the result of your SQL query as JSON and then deserialize the results to your object model rather than trying to map Read more…
If you’re using Entity Framework with a legacy database then you may well have single character status flags in some of the columns such as “O” = Operational, “M” = Marketing. Ideally these would be numeric IDs that match to a separate status table which would allow the IDs to Read more…
In a similar vein to my post on storing complex properties of a TableEntity in Azure Table Storage it’s also possible to store Enum text values by using custom attributes to control serialization/deserialization. ReceiptRequestEntity.cs EntityEnumPropertyConverterAttribute.cs
If you want to insert a row into an Azure Table Storage table the easiest way is to create a new class with the desired fields that inherits from TableEntity perform an insert operation with it using the storage client. This works fine as long as long as the properties Read more…
Azure Table storage is a way of storing structured NoSQL data in the cloud, as such it’s more geared towards rapid read access rather than manipulation of data in the table. If you want to perform any operations such as updates or deletes on data in your table then the Read more…