Check whether text is valid JSON.
Reject malformed input before processing it.
SELECT json_valid('{"ok":true}'), json_valid('{broken}');Expected output EXAMPLE
1|0
Details
Requires SQLite 3.40 or later. Run with sqlite3 demo.db in a scratch directory. Result rows below use | between columns, without headers; client display formatting may differ. The function returns one for valid JSON and zero for invalid JSON. The verifier uses a fresh SQLite file for each example.
Tested on Ubuntu 24.04.5 LTS · · SQLite 3.45.1 · sqlite3 3.45.1-1ubuntu2.8
Test inputs, results and environment
The exact published code ran in a dedicated Linux test container with prepared inputs. Snippet process uid 65534 with a read-only root filesystem and temporary working files. Networking disabled. Fixtures and output records are isolated from the application database. Testing covers this example and its stated checks, not every input, operating system, or runtime version. The Linux container shares its host's kernel; this is not a native Windows test.
- Architecture / host kernel
- x86_64 / 6.18.54.1-microsoft-standard-WSL2
- Snippet identity / locale
- uid=65534, gid=65534 (unprivileged process) / C.UTF-8
- Interpreter invocation
Execute the exact SQL in a fresh database/schema; serialize result rows with | separators- Container image ID
sha256:ec91410a8f6ec3e985830b5e3a0560306d36f8c1c5ccd91a6699abe707123fa3- Code SHA-256
b552a6c3ec1ffea0f4752e8d096a19f33c75e1ba645bcfd072b498feb3e714f8- Dependencies
- sqlite3 3.45.1-1ubuntu2.8
Test input setup
These are the prepared inputs used by the test harness. See Details above for the prerequisites and how to run this example.
# No input files required.
Observed standard output
1|0
Exit code: 0. Standard error: empty. Validation: Exact stdout comparison. System-dependent values above are one recorded run.