Module import 

Bulk import: a file’s rows written through a resource’s form, with a report.

A resource declaring import: true gets the pages under its own path: a file taken in, its columns shown beside the form’s fields with a match proposed for each, a check that writes nothing, then the run and its report as it fills. Each row is written the way the form’s own submit would: the same rules, field types, listeners, persister and audit entry, one commit a row. The run is detached from the request that started it and keeps its counts and notes in a table the report polls, so a long file finishes whether or not the browser waits, and a refused row is a line in the report, never a stopped import. From code, start and find do the same without the pages.

Re-exports

pub use run::find;

pub use run::start;

pub use run::Duplicates;

pub use run::Match;

pub use run::Note;

pub use run::NoteKind;

pub use run::OnMatch;

pub use run::Run;

pub use run::RunError;

pub use run::RunSpec;

pub use run::Status;

Modules

run

The run: a file’s rows through a form, detached from the request, with a report a screen polls.

schema

The table and column identifiers.

Structs

ImportModule

The laterite.import module: the run table. Built in.

Constants

DISK

The name of the disk uploaded files are stored on. The application may register a laterite_media::DiskReg under it; without one, the files go to private under the configured storage directory.