EncryptedSqliteBlobCache(string, string, IScheduler?, bool) constructor¶
Defined in
Type: EncryptedSqliteBlobCache
Namespace: ReactiveMarbles.CacheDatabase.EncryptedSqlite3
Assembly: ReactiveMarbles.CacheDatabase.EncryptedSqlite3.dll
Applies to
netstandard2.0
Overloads¶
- 1.
public EncryptedSqliteBlobCache(string fileName, string password, IScheduler? scheduler = null, bool storeDateTimeAsTicks = true) - 2.
public EncryptedSqliteBlobCache(SQLiteConnectionString connectionString, IScheduler? scheduler = null)
1. Overload¶
public EncryptedSqliteBlobCache(string fileName, string password, IScheduler? scheduler = null, bool storeDateTimeAsTicks = true)
Summary: Initializes a new instance of the EncryptedSqliteBlobCache class.
Parameters
| Name | Type | Description |
|---|---|---|
fileName | string | The database file name. |
password | string | The password. |
scheduler = null | [IScheduler?](# | The scheduler. |
storeDateTimeAsTicks = true | bool | Specifies whether to store DateTime properties as ticks (true) or strings (false). You absolutely do want to store them as Ticks in all new projects. The value of false is only here for backwards compatibility. There is a significant speed advantage, with no down sides, when setting storeDateTimeAsTicks = true. If you use DateTimeOffset properties, it will be always stored as ticks regardingless the storeDateTimeAsTicks parameter. |
2. Overload¶
public EncryptedSqliteBlobCache(SQLiteConnectionString connectionString, IScheduler? scheduler = null)
Summary: Initializes a new instance of the EncryptedSqliteBlobCache class.
Parameters
| Name | Type | Description |
|---|---|---|
connectionString | SQLiteConnectionString | The connection string. |
scheduler = null | [IScheduler?](# | The scheduler. |