LogStoreException class final
A failure of a store's backend (SQLite, a file, a remote service) in a store operation: what the application needs to handle or report it, without the query parameters, which for a write are the whole entry.
Backend exceptions tend to print their parameters in toString()
(SqliteException from package:sqlite3 does), and a store failure goes
to diagnostics (LogStoreSink: the store failed to write …) and from there
to the console or the application's handler (Sentry), where log contents
do not belong. So a store rethrows backend failures in this form, with the
original stack trace (Error.throwWithStackTrace), and application code
handles every store the same way. Exceptions from opening a database are
not wrapped: they have no parameters, and there is no store yet.
- Implemented types
- Annotations
-
- @immutable
Constructors
- LogStoreException(String message, {int? code, String? operation, String? statement})
-
const
Properties
- code → int?
-
Backend result code, if the backend has one: for SQLite the extended
result code (
SQLITE_FULL,SQLITE_BUSY, …).final - hashCode → int
-
The hash code for this object.
no setterinherited
- message → String
-
Backend message, with its explanation if it gives one separately.
final
- operation → String?
-
The backend operation during which the failure occurred, if known.
final
- runtimeType → Type
-
A representation of the runtime type of the object.
no setterinherited
- statement → String?
-
The statement that failed, if known, without parameters.
final
Methods
-
noSuchMethod(
Invocation invocation) → dynamic -
Invoked when a nonexistent method or property is accessed.
inherited
-
toString(
) → String -
A string representation of this object.
override
Operators
-
operator ==(
Object other) → bool -
The equality operator.
inherited