Constructor. Fields are added externally by the blob implementation
via initializeApiDatamodel.
the OINOBlobApi that owns this data model
ReadonlyapiDatabase refererence of the table
ReadonlyblobReference to the owning blob API
ReadonlyfieldsField refererences of the API
Convert an array of blob entries into an in-memory dataset whose columns match the fields present in this model.
blob entries from the storage backend
Find all fields based of given filter callback criteria (e.g. fields of certain data type, primary keys etc.)
callback called for each field to include or not
Find a field of a given name if any.
name of the field to find
Find index of a field of a given name if any.
name of the field to find
Return the primary key values of one row in order of the data model
data row
apply hashid when applicable
Pring debug information for the field
length of the debug output (or 0 for as long as needed)
Print debug information about the fields.
string to separate field prints
Print all public properties (db, table name, fields) of the datamodel. Used in automated testing validate schema has stayed the same.
Static data model for blob listings.
Fields are added by the blob implementation's
initializeApiDatamodelmethod, so the exact set depends on what the storage backend supports. The canonical order is:name– full blob name (primary key, string)etag– entity tag (string)lastModified– last modification timestamp (datetime)contentLength– size in bytes (number)contentType– MIME type (string) – omitted when not supported