Namespace Serenity.StructuredPersistence.Infrastructure.Settings

Classes

UnityDatabaseBackendDefinition

Abstract intermediate base for the server database structured-store backends (Postgres/MySql/Mongo), which share the same discrete connection fields, the same connection-string override, and the same environment-variable override mechanism.

UnityHttpBackendDefinition

Connection configuration for a remote HTTP structured-store service, shareable by every structured-store consumer.

UnityLocalFileBackendDefinition

Structured-store backend writing each partition as a human-readable, pretty-printed JSON file under a subdirectory of UnityEngine.Application.persistentDataPath. No external service or driver is needed. Consumer-agnostic: each consumer decides its own default directory when no asset (or a blank DirectoryName) is provided.

UnityMongoBackendDefinition

Connection configuration for a MongoDB structured-store server, shareable by every structured-store consumer.

UnityMySqlBackendDefinition

Connection configuration for a MySQL structured-store server, shareable by every structured-store consumer.

UnityPlayerPrefsBackendDefinition

Structured-store backend storing records in the device's PlayerPrefs, binary-encoded. Requires no configuration and cannot fail to construct. PlayerPrefs has platform-specific size limits; prefer UnityLocalFileBackendDefinition for durable, inspectable history.

UnityPostgresBackendDefinition

Connection configuration for a PostgreSQL structured-store server, shareable by every structured-store consumer.

UnitySqliteBackendDefinition

Structured-store backend writing records to an embedded SQLite database file. No external service is needed, only the driver: consumers require the SERENITY_STRUCTURED_SQLITE scripting define and the Microsoft.Data.Sqlite driver. Consumer-agnostic: each consumer decides its own default file name when no asset (or a blank DatabaseFileName) is provided.

UnityStructuredBackendDefinition

Abstract base for shareable, consumer-agnostic server connection assets used by structured persistence backends. A concrete asset (Http/Postgres/MySql/Mongo) holds ONLY connection configuration — no consumer-specific fields — so the same server asset can be referenced by any structured-store consumer (structured logging today, leaderboard later).