From a0a408e416c19e06e8f298acdacfe4e99eb17fed Mon Sep 17 00:00:00 2001
From: Magnus Persson <1431685+magnusp@users.noreply.github.com>
Date: Sat, 24 Oct 2026 02:21:59 +0200
Subject: [PATCH] docs(conformance): make the query string part of the
 namespace identity

The URL mapping section said the query string was ignored, which contradicted XerialConformanceDriver.plan() and the harness tests. State that a different query string addresses a different namespace and that the option values are not applied to the server.
---
 libsql-conformance/README.md | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/libsql-conformance/README.md b/libsql-conformance/README.md
index 8100b25..d079b32 100644
--- a/libsql-conformance/README.md
+++ b/libsql-conformance/README.md
@@ -164,8 +164,10 @@ same namespace; for example, `data/example.db` and `/work/data/example.db` match
 the process working directory is `/work`. Normalization resolves `.` and `..` but does
 not resolve symbolic links.
 
-The query string is ignored when deriving the namespace, so URL pragmas such as
-`?journal_mode=WAL` have no effect on the conformance server. No local SQLite file is
+The query string is part of the namespace identity, so two URLs that differ only in
+their query string address different namespaces. The option values themselves are not
+applied to the conformance server; a URL pragma such as `?journal_mode=WAL` selects a
+separate namespace rather than changing server behavior. No local SQLite file is
 created; the data lives in the sqld namespace.
 
 ## Persistence