Initialise the Azure SDK table client. Does not perform any network call.
Delete an entity.
[partitionKey, rowKey]
Release the client reference.
Fetch a single entity by its primary key values.
[partitionKey, rowKey]
Attach a static OINONoSqlDataModel to the given API, adding all five
standard fields.
the OINONoSqlApi whose data model is to be initialised
List entities from the table, applying native OData filtering for
partitionKey, rowKey, and timestamp predicates server-side, and
performing in-memory evaluation for the remaining predicates.
Optionalfilter: OINOQueryFilteroptional query filter to apply
Batch-upsert using Azure Table Storage transactions. Each transaction is limited to 100 entities that share the same partition key. Entries are grouped by partition key first, then chunked to satisfy the limit.
Upsert (insert or replace) an entity.
All fields in entry.properties are written as top-level entity
properties in Azure Table Storage.
entity to upsert
Verify that the target table exists and is accessible.
StaticfilterAttempt to translate an OINOQueryFilter tree to an Azure Table Storage
OData v3 filter expression string.
Returns undefined for sub-trees that contain untranslatable predicates
(e.g. filter on etag, or a like comparison). The caller falls back
to in-memory evaluation for those cases.
filter to translate
Azure Table Storage implementation of
OINONoSql.Authenticates using an Azure Storage connection string. Connection parameters map as:
params.url→ table service endpoint, e.g.https://<account>.table.core.windows.netparams.table→ table nameparams.connectionStr→ Azure Storage connection string (e.g.DefaultEndpointsProtocol=https;AccountName=...)Register and use via the factory:
Static partition key
Set
staticPartitionKeyin the params to scope all operations to a fixed partition key. This lets multiple logical tables share one physical Azure Table Storage table:Filter support
Filters on
partitionKey,rowKey, andtimestampare translated to native Azure Table Storage OData query filter expressions and evaluated server-side. Filters onetagare evaluated in-memory after the listing.OData operators supported:
eq,ne,lt,le,gt,ge,and,or,not. Thelikeoperator is not supported by OData and is evaluated in-memory.