package granary

You can search for identifiers within the package.

in-package search v0.2.0

Pure-OCaml SQL engine

Install

dune-project

Dependency

github.com Edit opam file Versions (1)

Authors

T

Tej Pochiraju <foss@tej.sh>

Maintainers

T

Tej Pochiraju <foss@tej.sh>

Sources

0.0.3.tar.gz

sha256=8b18780ea373be48301d9f333925860a2f9110fc0ac28684295118d72b65a67e

sha512=25ca3c9c5e2b528704a542502e0f37dc33ba003f65622d969b8c2b800778585f8ef0cf89b36e6679832e3993e8303aecddfc662742baf7044d6afe4a796b8f11

doc/granary.sample/Granary_sample/Sample/index.html

Module `Granary_sample.Sample`Source

Shared granary demo workload (#403).

Exercised by both the sample MirageOS unikernel (mirage/unikernel.ml) and the host smoke test (test/test_mirage_unikernel_smoke.ml) so the two package the same engine workload over a Granary_store.Store opened in WAL mode.

Sourceval run_demo : Granary.Db.t -> (int, Granary.Db.error) result Lwt.t

run_demo db runs a small, deterministic workload against db: creates a table, inserts three rows inside an explicit transaction, commits, and reads the rows back. On success it returns the number of rows read back (always 3).

The explicit BEGIN/COMMIT drives the engine's WAL fsync / commit path, so the on-disk byte ordering of pages and WAL frames is exercised end-to-end — the arch-neutral concern behind #402/#403.