graphitesql 0.1.0

A pure, safe, no_std Rust re-implementation of SQLite, compatible with the SQLite 3 file format.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109

//! The `sqlite3` CLI runs each trailing command-line argument as an independent
//! SQL batch: `sqlite3 db "SELECT 1" "SELECT 2"` executes both, even though
//! neither argument ends in `;`. graphite's CLI previously joined the arguments
//! into one string with a single space, so two complete-but-unterminated
//! statements were spliced together (`…VALUES(1),(2)` + `SELECT …` →
//! `…(2)SELECT …`) and reported as a syntax error. Verified against the sqlite3
//! 3.50.4 CLI.

#![cfg(feature = "std")]

use std::process::Command;

fn sqlite3_available() -> bool {
    Command::new("sqlite3").arg("--version").output().is_ok()
}

/// Run `bin :memory: <args…>` and return stdout (trimmed) or the first non-caret
/// error line with the CLI framing stripped.
fn run(bin: &str, args: &[&str]) -> String {
    let out = Command::new(bin)
        .arg(":memory:")
        .args(args)
        .output()
        .unwrap();
    let stdout = String::from_utf8_lossy(&out.stdout);
    if !stdout.trim().is_empty() {
        return stdout.trim_end().to_string();
    }
    String::from_utf8_lossy(&out.stderr)
        .lines()
        .find(|l| !l.trim_start().starts_with('^'))
        .unwrap_or("")
        .trim_start_matches("Error: in prepare, ")
        .trim_start_matches("Error: stepping, ")
        .trim_start_matches("Error: ")
        .trim_start_matches("SQL error: ")
        .trim_start_matches("error: ")
        .trim_end()
        .to_string()
}

#[test]
fn each_argument_runs_as_its_own_batch() {
    let g = env!("CARGO_BIN_EXE_graphitesql");
    // Neither argument is `;`-terminated, yet both must run.
    assert_eq!(
        run(
            g,
            &[
                "CREATE TABLE t(a); INSERT INTO t VALUES(1),(2)",
                "SELECT a FROM t"
            ]
        ),
        "1\n2"
    );
    // Three separate arguments, each a single statement.
    assert_eq!(
        run(
            g,
            &[
                "CREATE TABLE t(a)",
                "INSERT INTO t VALUES(7)",
                "SELECT a FROM t"
            ]
        ),
        "7"
    );
    // A single combined argument with internal `;` still works as before.
    assert_eq!(
        run(
            g,
            &["CREATE TABLE t(a); INSERT INTO t VALUES(9); SELECT a FROM t;"]
        ),
        "9"
    );
}

#[test]
fn first_failing_argument_aborts_the_rest() {
    let g = env!("CARGO_BIN_EXE_graphitesql");
    // The first argument errors, so the second never produces output.
    assert_eq!(run(g, &["SELECT", "SELECT 1"]), "incomplete input");
}

#[test]
fn matches_sqlite_cli() {
    if !sqlite3_available() {
        eprintln!("sqlite3 CLI not found; skipping");
        return;
    }
    let g = env!("CARGO_BIN_EXE_graphitesql");
    let cases: &[&[&str]] = &[
        &[
            "CREATE TABLE t(a); INSERT INTO t VALUES(1),(2)",
            "SELECT a FROM t",
        ],
        &[
            "CREATE TABLE t(a)",
            "INSERT INTO t VALUES(7)",
            "SELECT a FROM t",
        ],
        &["SELECT 1", "SELECT 2"],
        &["CREATE TABLE t(a); INSERT INTO t VALUES(9); SELECT a FROM t;"],
        &["SELECT", "SELECT 1"],
    ];
    for args in cases {
        assert_eq!(run("sqlite3", args), run(g, args), "for {args:?}");
    }
}