sqlite

Documentation

Overview

Package sqlite provides SQLite backend.

Design principles

1. Transactions should be avoided when possible. That's because there can be, at most, one write transaction at a given time for the whole database. (Note that there is a separate branch of SQLite with concurrent transactions, but it is not merged yet.) FerretDB often could use more granular locks - for example, per collection.
2. Explicit transaction retries and SQLITE_BUSY handling should be avoided - see above. Additionally, SQLite retries automatically with the busy_timeout parameter we set by default, which should be enough.
3. Metadata is heavily cached to avoid most queries and transactions.

Index

• func NewBackend(params *NewBackendParams) (backends.Backend, error)
• type NewBackendParams

Functions

func NewBackend

func NewBackend(params *NewBackendParams) (backends.Backend, error)

NewBackend creates a new Backend.

Types

type NewBackendParams

type NewBackendParams struct {
	URI       string
	L         *zap.Logger
	P         *state.Provider
	BatchSize int
	// contains filtered or unexported fields
}

NewBackendParams represents the parameters of NewBackend function.