test-data-service 0.2.0__tar.gz → 0.3.0__tar.gz

{test_data_service-0.2.0/src/test_data_service.egg-info → test_data_service-0.3.0}/PKG-INFO

@@ -1,8 +1,8 @@
 Metadata-Version: 2.4
 Name: test-data-service
-Version: 0.2.0
+Version: 0.3.0
 Summary: A disk-backed test data service with a REST API and web interface
-Author-email: Roy de Kleijn <dekleijn.roy@gmail.com>
+Author-email: Roy de Kleijn <info@testsmith.io>
 License: MIT
 Project-URL: Homepage, https://github.com/testsmith-io/test-data-service
 Project-URL: Documentation, https://github.com/testsmith-io/test-data-service#readme
@@ -81,46 +81,68 @@ port: 8000
 
 ### Data model
 
-Each entry is a `key` / `value` pair inside a **namespace**. A value is one
-of four types: `string`, `boolean`, `number`, or `array`. The type is stored
-alongside the value and validated on write.
+Three levels: **namespace → table → row**.
+
+* A **namespace** is the unit of access control.
+* A namespace holds any number of **tables**.
+* A table holds **rows**, and each row is a record with an **arbitrary set of
+  fields**. Field values can be any JSON (string, number, boolean, array,
+  object, null).
+* A table can also have **designed columns** — a persisted column list you set
+  up front (the "schema"), which shows even before any rows exist. The
+  *effective* columns of a table are its designed columns plus any extra fields
+  that appear in its rows, so the layout stays dynamic.
 
 ### REST API
 
-`POST` targets the namespace (collection) with the key **in the body**; `PUT`
-targets a specific entry URI. They are not interchangeable — `POST` only creates,
-`PUT` only updates.
-
-| Method   | Path                    | Permission | Description                          |
-|----------|-------------------------|------------|--------------------------------------|
-| `GET`    | `/api/health`           | —          | Health + auth status                 |
-| `GET`    | `/api/whoami`           | —          | Caller's access summary              |
-| `GET`    | `/api/namespaces`       | any key    | List accessible namespaces           |
-| `GET`    | `/api/{ns}`             | read `ns`  | List entries in a namespace          |
-| `POST`   | `/api/{ns}`             | write `ns` | Create an entry (`409` if key exists) |
-| `GET`    | `/api/{ns}/{key}`       | read `ns`  | Get one entry                        |
-| `PUT`    | `/api/{ns}/{key}`       | write `ns` | Update an entry (`404` if missing)   |
-| `DELETE` | `/api/{ns}/{key}`       | write `ns` | Delete an entry                      |
-| `DELETE` | `/api/{ns}`             | write `ns` | Delete a namespace                   |
+| Method   | Path                              | Permission | Description                     |
+|----------|-----------------------------------|------------|---------------------------------|
+| `GET`    | `/api/health`                     | —          | Health + auth status            |
+| `GET`    | `/api/whoami`                     | —          | Caller's access summary         |
+| `GET`    | `/api/namespaces`                 | any key    | List accessible namespaces      |
+| `POST`   | `/api/namespaces`                 | admin      | Create a namespace              |
+| `DELETE` | `/api/{ns}`                       | write `ns` | Delete a namespace              |
+| `GET`    | `/api/{ns}`                       | read `ns`  | List tables                     |
+| `POST`   | `/api/{ns}`                       | write `ns` | Create a table (`{"name": …}`)  |
+| `GET`    | `/api/{ns}/{table}`               | read `ns`  | Get a table's designed columns  |
+| `PUT`    | `/api/{ns}/{table}`               | write `ns` | Design columns (`{"columns":[…]}`) |
+| `DELETE` | `/api/{ns}/{table}`               | write `ns` | Delete a table                  |
+| `GET`    | `/api/{ns}/{table}/rows`          | read `ns`  | List rows (filter with `?col=value`) |
+| `POST`   | `/api/{ns}/{table}/rows`          | write `ns` | Create a row (body = its fields)|
+| `GET`    | `/api/{ns}/{table}/rows/{id}`     | read `ns`  | Get one row                     |
+| `PUT`    | `/api/{ns}/{table}/rows/{id}`     | write `ns` | Replace a row's fields          |
+| `DELETE` | `/api/{ns}/{table}/rows/{id}`     | write `ns` | Delete a row                    |
+
+In the web UI, open a table and use the **Columns** designer to add/remove
+columns; they persist and appear in the grid and the add-row form even with no
+rows yet.
 
 ```bash
-# create — POST to the namespace, key in the body
-curl -X POST localhost:8000/api/demo \
-  -H 'Content-Type: application/json' \
-  -d '{"key":"greeting","value":"hello","type":"string"}'
+curl -X POST localhost:8000/api/namespaces -H 'Content-Type: application/json' -d '{"name":"demo"}'
+curl -X POST localhost:8000/api/demo       -H 'Content-Type: application/json' -d '{"name":"users"}'
 
-# update — PUT to the entry's URI
-curl -X PUT localhost:8000/api/demo/greeting \
+# a row IS its fields — any shape you like
+curl -X POST localhost:8000/api/demo/users/rows \
   -H 'Content-Type: application/json' \
-  -d '{"value":"hi there","type":"string"}'
+  -d '{"name":"alice","age":30,"active":true}'
+# -> {"id":"<row-id>","updated_at":"...","fields":{...}}
 
-curl localhost:8000/api/demo          # list entries
+curl localhost:8000/api/demo/users/rows
+# -> {"columns":["name","age","active", ...], "rows":[{"id":..., "fields":{...}}, ...]}
+
+# filter by column conditions — each query param is a column=value test,
+# and multiple are AND-ed together:
+curl "localhost:8000/api/demo/users/rows?status=ok&ean=123"
 ```
 
-(The names `namespaces`, `health`, and `whoami` are reserved and can't be used
-as namespaces, since they'd collide with the routes above.)
+Filter values are matched leniently: `ean=123` matches a numeric `123` or the
+string `"123"`, `active=true` matches the boolean. The web UI has a matching
+**filter** box on each table (type `status=ok&ean=123`).
+
+(The names `namespaces`, `health`, `whoami`, `keys`, `accounts`, `login`,
+`logout`, `password`, and `me` are reserved and can't be used as namespaces.)
 
-The API is self-documenting via OpenAPI. Interactive docs are available at:
+The API is self-documenting via OpenAPI:
 
 - **`/docs`** — Swagger UI (also linked as **API docs** in the web interface header)
 - **`/redoc`** — ReDoc
@@ -129,24 +151,20 @@ The API is self-documenting via OpenAPI. Interactive docs are available at:
 When auth is enabled, each operation in Swagger exposes an `X-API-Key` header
 field you can fill in to try requests.
 
-### CSV import / export (web UI only)
+### CSV import / export (web UI only, per table)
 
-The web interface has **Download CSV** / **Import CSV** buttons on each
-namespace. These are a convenience of the web UI only — they are built on the
-regular entry API (export reads the entries; import creates/updates each row),
-so there are no dedicated CSV endpoints. The CSV has three columns —
-`key`, `type`, `value`:
+Each table in the web UI has **Download CSV** / **Import CSV** buttons. A table
+maps naturally to CSV: the header row is the column names, each line is a row.
+These are built on the rows API (no dedicated CSV endpoints). On import, each
+cell is parsed leniently — `30` → number, `true` → boolean, `[1,2]` → array,
+anything else → string.
 
 ```csv
-key,type,value
-name,string,alice
-count,number,7
-tags,array,"[""x"", ""y""]"
+name,age,active
+alice,30,true
+bob,25,false
 ```
 
-On import the `type` column is optional — if omitted, each value's type is
-inferred from its text.
-
 ### Access control (accounts + API keys)
 
 Off by default. **Turn it on** with `auth: true` in `tds.yml`, `--auth`, or
@@ -182,9 +200,9 @@ Each signed-in user can mint a personal **API key** (web UI → *My API keys*, o
 
 ```bash
 # the token is returned once; then use it as a header
-curl -X POST localhost:8000/api/projects \
+curl -X POST localhost:8000/api/projects/people/rows \
   -H "X-API-Key: $TOKEN" -H "Content-Type: application/json" \
-  -d '{"key":"env","value":"staging","type":"string"}'
+  -d '{"name":"alice","role":"qa"}'
 ```
 
 #### Auth & admin endpoints (summary)
@@ -211,7 +229,9 @@ environment variables:
 
 | YAML key   | Env var            | Default      | Purpose                                  |
 |------------|--------------------|--------------|------------------------------------------|
-| `data_dir` | `TDS_DATA_DIR`     | `./tds-data` | Namespace files + `.auth/` live here     |
+| `data_dir` | `TDS_DATA_DIR`     | `./tds-data` | Data + `.auth/` live here                |
+| `storage`  | `TDS_STORAGE`      | `sqlite`     | Storage backend: `sqlite` or `file`      |
+| `db_path`  | `TDS_DB_PATH`      | `<data_dir>/tds.db` | SQLite DB path (sqlite backend)   |
 | `auth`     | `TDS_AUTH_ENABLED` | `false`      | Turn access control on/off               |
 | `host`     | —                  | `127.0.0.1`  | Bind host                                |
 | `port`     | —                  | `8000`       | Bind port                                |
@@ -220,8 +240,17 @@ environment variables:
 | `api_keys` | `TDS_API_KEYS`     | *(empty)*    | Seed machine keys + grants               |
 | —          | `TDS_KEY_PEPPER`   | *(empty)*    | Optional pepper for API-key hashing      |
 
-Credentials live under `<data_dir>/.auth/` (`accounts.json`, `keys.json`,
-`secret`) — all hashed/secret material, never plaintext passwords or tokens.
+#### Storage backend
+
+Data is kept in **SQLite** by default — a single `tds.db` file the app creates
+in `data_dir` on first start (no setup, no server). Rows store their dynamic
+fields in a JSON column, so the schema is fixed while the data stays free-form.
+Set `storage: file` to use one JSON file per namespace instead (human-readable
+and dependency-free, but it rewrites a whole file per change and isn't safe
+across processes). Either way, point `data_dir` at a persistent volume.
+
+Credentials always live under `<data_dir>/.auth/` (`accounts.json`,
+`keys.json`, `secret`) — hashed/secret material, never plaintext.
 
 ### Tests
 

{test_data_service-0.2.0 → test_data_service-0.3.0}/pyproject.toml

@@ -4,13 +4,13 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "test-data-service"
-version = "0.2.0"
+version = "0.3.0"
 description = "A disk-backed test data service with a REST API and web interface"
 readme = "readme.md"
 requires-python = ">=3.10"
 license = { text = "MIT" }
 authors = [
-    { name = "Roy de Kleijn", email = "dekleijn.roy@gmail.com" },
+    { name = "Roy de Kleijn", email = "info@testsmith.io" },
 ]
 keywords = ["test-data", "rest", "api", "fastapi", "key-value", "testing", "mock-data"]
 classifiers = [

{test_data_service-0.2.0 → test_data_service-0.3.0}/readme.md

@@ -43,46 +43,68 @@ port: 8000
 
 ### Data model
 
-Each entry is a `key` / `value` pair inside a **namespace**. A value is one
-of four types: `string`, `boolean`, `number`, or `array`. The type is stored
-alongside the value and validated on write.
+Three levels: **namespace → table → row**.
+
+* A **namespace** is the unit of access control.
+* A namespace holds any number of **tables**.
+* A table holds **rows**, and each row is a record with an **arbitrary set of
+  fields**. Field values can be any JSON (string, number, boolean, array,
+  object, null).
+* A table can also have **designed columns** — a persisted column list you set
+  up front (the "schema"), which shows even before any rows exist. The
+  *effective* columns of a table are its designed columns plus any extra fields
+  that appear in its rows, so the layout stays dynamic.
 
 ### REST API
 
-`POST` targets the namespace (collection) with the key **in the body**; `PUT`
-targets a specific entry URI. They are not interchangeable — `POST` only creates,
-`PUT` only updates.
-
-| Method   | Path                    | Permission | Description                          |
-|----------|-------------------------|------------|--------------------------------------|
-| `GET`    | `/api/health`           | —          | Health + auth status                 |
-| `GET`    | `/api/whoami`           | —          | Caller's access summary              |
-| `GET`    | `/api/namespaces`       | any key    | List accessible namespaces           |
-| `GET`    | `/api/{ns}`             | read `ns`  | List entries in a namespace          |
-| `POST`   | `/api/{ns}`             | write `ns` | Create an entry (`409` if key exists) |
-| `GET`    | `/api/{ns}/{key}`       | read `ns`  | Get one entry                        |
-| `PUT`    | `/api/{ns}/{key}`       | write `ns` | Update an entry (`404` if missing)   |
-| `DELETE` | `/api/{ns}/{key}`       | write `ns` | Delete an entry                      |
-| `DELETE` | `/api/{ns}`             | write `ns` | Delete a namespace                   |
+| Method   | Path                              | Permission | Description                     |
+|----------|-----------------------------------|------------|---------------------------------|
+| `GET`    | `/api/health`                     | —          | Health + auth status            |
+| `GET`    | `/api/whoami`                     | —          | Caller's access summary         |
+| `GET`    | `/api/namespaces`                 | any key    | List accessible namespaces      |
+| `POST`   | `/api/namespaces`                 | admin      | Create a namespace              |
+| `DELETE` | `/api/{ns}`                       | write `ns` | Delete a namespace              |
+| `GET`    | `/api/{ns}`                       | read `ns`  | List tables                     |
+| `POST`   | `/api/{ns}`                       | write `ns` | Create a table (`{"name": …}`)  |
+| `GET`    | `/api/{ns}/{table}`               | read `ns`  | Get a table's designed columns  |
+| `PUT`    | `/api/{ns}/{table}`               | write `ns` | Design columns (`{"columns":[…]}`) |
+| `DELETE` | `/api/{ns}/{table}`               | write `ns` | Delete a table                  |
+| `GET`    | `/api/{ns}/{table}/rows`          | read `ns`  | List rows (filter with `?col=value`) |
+| `POST`   | `/api/{ns}/{table}/rows`          | write `ns` | Create a row (body = its fields)|
+| `GET`    | `/api/{ns}/{table}/rows/{id}`     | read `ns`  | Get one row                     |
+| `PUT`    | `/api/{ns}/{table}/rows/{id}`     | write `ns` | Replace a row's fields          |
+| `DELETE` | `/api/{ns}/{table}/rows/{id}`     | write `ns` | Delete a row                    |
+
+In the web UI, open a table and use the **Columns** designer to add/remove
+columns; they persist and appear in the grid and the add-row form even with no
+rows yet.
 
 ```bash
-# create — POST to the namespace, key in the body
-curl -X POST localhost:8000/api/demo \
-  -H 'Content-Type: application/json' \
-  -d '{"key":"greeting","value":"hello","type":"string"}'
+curl -X POST localhost:8000/api/namespaces -H 'Content-Type: application/json' -d '{"name":"demo"}'
+curl -X POST localhost:8000/api/demo       -H 'Content-Type: application/json' -d '{"name":"users"}'
 
-# update — PUT to the entry's URI
-curl -X PUT localhost:8000/api/demo/greeting \
+# a row IS its fields — any shape you like
+curl -X POST localhost:8000/api/demo/users/rows \
   -H 'Content-Type: application/json' \
-  -d '{"value":"hi there","type":"string"}'
+  -d '{"name":"alice","age":30,"active":true}'
+# -> {"id":"<row-id>","updated_at":"...","fields":{...}}
+
+curl localhost:8000/api/demo/users/rows
+# -> {"columns":["name","age","active", ...], "rows":[{"id":..., "fields":{...}}, ...]}
 
-curl localhost:8000/api/demo          # list entries
+# filter by column conditions — each query param is a column=value test,
+# and multiple are AND-ed together:
+curl "localhost:8000/api/demo/users/rows?status=ok&ean=123"
 ```
 
-(The names `namespaces`, `health`, and `whoami` are reserved and can't be used
-as namespaces, since they'd collide with the routes above.)
+Filter values are matched leniently: `ean=123` matches a numeric `123` or the
+string `"123"`, `active=true` matches the boolean. The web UI has a matching
+**filter** box on each table (type `status=ok&ean=123`).
+
+(The names `namespaces`, `health`, `whoami`, `keys`, `accounts`, `login`,
+`logout`, `password`, and `me` are reserved and can't be used as namespaces.)
 
-The API is self-documenting via OpenAPI. Interactive docs are available at:
+The API is self-documenting via OpenAPI:
 
 - **`/docs`** — Swagger UI (also linked as **API docs** in the web interface header)
 - **`/redoc`** — ReDoc
@@ -91,24 +113,20 @@ The API is self-documenting via OpenAPI. Interactive docs are available at:
 When auth is enabled, each operation in Swagger exposes an `X-API-Key` header
 field you can fill in to try requests.
 
-### CSV import / export (web UI only)
+### CSV import / export (web UI only, per table)
 
-The web interface has **Download CSV** / **Import CSV** buttons on each
-namespace. These are a convenience of the web UI only — they are built on the
-regular entry API (export reads the entries; import creates/updates each row),
-so there are no dedicated CSV endpoints. The CSV has three columns —
-`key`, `type`, `value`:
+Each table in the web UI has **Download CSV** / **Import CSV** buttons. A table
+maps naturally to CSV: the header row is the column names, each line is a row.
+These are built on the rows API (no dedicated CSV endpoints). On import, each
+cell is parsed leniently — `30` → number, `true` → boolean, `[1,2]` → array,
+anything else → string.
 
 ```csv
-key,type,value
-name,string,alice
-count,number,7
-tags,array,"[""x"", ""y""]"
+name,age,active
+alice,30,true
+bob,25,false
 ```
 
-On import the `type` column is optional — if omitted, each value's type is
-inferred from its text.
-
 ### Access control (accounts + API keys)
 
 Off by default. **Turn it on** with `auth: true` in `tds.yml`, `--auth`, or
@@ -144,9 +162,9 @@ Each signed-in user can mint a personal **API key** (web UI → *My API keys*, o
 
 ```bash
 # the token is returned once; then use it as a header
-curl -X POST localhost:8000/api/projects \
+curl -X POST localhost:8000/api/projects/people/rows \
   -H "X-API-Key: $TOKEN" -H "Content-Type: application/json" \
-  -d '{"key":"env","value":"staging","type":"string"}'
+  -d '{"name":"alice","role":"qa"}'
 ```
 
 #### Auth & admin endpoints (summary)
@@ -173,7 +191,9 @@ environment variables:
 
 | YAML key   | Env var            | Default      | Purpose                                  |
 |------------|--------------------|--------------|------------------------------------------|
-| `data_dir` | `TDS_DATA_DIR`     | `./tds-data` | Namespace files + `.auth/` live here     |
+| `data_dir` | `TDS_DATA_DIR`     | `./tds-data` | Data + `.auth/` live here                |
+| `storage`  | `TDS_STORAGE`      | `sqlite`     | Storage backend: `sqlite` or `file`      |
+| `db_path`  | `TDS_DB_PATH`      | `<data_dir>/tds.db` | SQLite DB path (sqlite backend)   |
 | `auth`     | `TDS_AUTH_ENABLED` | `false`      | Turn access control on/off               |
 | `host`     | —                  | `127.0.0.1`  | Bind host                                |
 | `port`     | —                  | `8000`       | Bind port                                |
@@ -182,8 +202,17 @@ environment variables:
 | `api_keys` | `TDS_API_KEYS`     | *(empty)*    | Seed machine keys + grants               |
 | —          | `TDS_KEY_PEPPER`   | *(empty)*    | Optional pepper for API-key hashing      |
 
-Credentials live under `<data_dir>/.auth/` (`accounts.json`, `keys.json`,
-`secret`) — all hashed/secret material, never plaintext passwords or tokens.
+#### Storage backend
+
+Data is kept in **SQLite** by default — a single `tds.db` file the app creates
+in `data_dir` on first start (no setup, no server). Rows store their dynamic
+fields in a JSON column, so the schema is fixed while the data stays free-form.
+Set `storage: file` to use one JSON file per namespace instead (human-readable
+and dependency-free, but it rewrites a whole file per change and isn't safe
+across processes). Either way, point `data_dir` at a persistent volume.
+
+Credentials always live under `<data_dir>/.auth/` (`accounts.json`,
+`keys.json`, `secret`) — hashed/secret material, never plaintext.
 
 ### Tests
 

{test_data_service-0.2.0 → test_data_service-0.3.0/src/test_data_service.egg-info}/PKG-INFO

@@ -1,8 +1,8 @@
 Metadata-Version: 2.4
 Name: test-data-service
-Version: 0.2.0
+Version: 0.3.0
 Summary: A disk-backed test data service with a REST API and web interface
-Author-email: Roy de Kleijn <dekleijn.roy@gmail.com>
+Author-email: Roy de Kleijn <info@testsmith.io>
 License: MIT
 Project-URL: Homepage, https://github.com/testsmith-io/test-data-service
 Project-URL: Documentation, https://github.com/testsmith-io/test-data-service#readme
@@ -81,46 +81,68 @@ port: 8000
 
 ### Data model
 
-Each entry is a `key` / `value` pair inside a **namespace**. A value is one
-of four types: `string`, `boolean`, `number`, or `array`. The type is stored
-alongside the value and validated on write.
+Three levels: **namespace → table → row**.
+
+* A **namespace** is the unit of access control.
+* A namespace holds any number of **tables**.
+* A table holds **rows**, and each row is a record with an **arbitrary set of
+  fields**. Field values can be any JSON (string, number, boolean, array,
+  object, null).
+* A table can also have **designed columns** — a persisted column list you set
+  up front (the "schema"), which shows even before any rows exist. The
+  *effective* columns of a table are its designed columns plus any extra fields
+  that appear in its rows, so the layout stays dynamic.
 
 ### REST API
 
-`POST` targets the namespace (collection) with the key **in the body**; `PUT`
-targets a specific entry URI. They are not interchangeable — `POST` only creates,
-`PUT` only updates.
-
-| Method   | Path                    | Permission | Description                          |
-|----------|-------------------------|------------|--------------------------------------|
-| `GET`    | `/api/health`           | —          | Health + auth status                 |
-| `GET`    | `/api/whoami`           | —          | Caller's access summary              |
-| `GET`    | `/api/namespaces`       | any key    | List accessible namespaces           |
-| `GET`    | `/api/{ns}`             | read `ns`  | List entries in a namespace          |
-| `POST`   | `/api/{ns}`             | write `ns` | Create an entry (`409` if key exists) |
-| `GET`    | `/api/{ns}/{key}`       | read `ns`  | Get one entry                        |
-| `PUT`    | `/api/{ns}/{key}`       | write `ns` | Update an entry (`404` if missing)   |
-| `DELETE` | `/api/{ns}/{key}`       | write `ns` | Delete an entry                      |
-| `DELETE` | `/api/{ns}`             | write `ns` | Delete a namespace                   |
+| Method   | Path                              | Permission | Description                     |
+|----------|-----------------------------------|------------|---------------------------------|
+| `GET`    | `/api/health`                     | —          | Health + auth status            |
+| `GET`    | `/api/whoami`                     | —          | Caller's access summary         |
+| `GET`    | `/api/namespaces`                 | any key    | List accessible namespaces      |
+| `POST`   | `/api/namespaces`                 | admin      | Create a namespace              |
+| `DELETE` | `/api/{ns}`                       | write `ns` | Delete a namespace              |
+| `GET`    | `/api/{ns}`                       | read `ns`  | List tables                     |
+| `POST`   | `/api/{ns}`                       | write `ns` | Create a table (`{"name": …}`)  |
+| `GET`    | `/api/{ns}/{table}`               | read `ns`  | Get a table's designed columns  |
+| `PUT`    | `/api/{ns}/{table}`               | write `ns` | Design columns (`{"columns":[…]}`) |
+| `DELETE` | `/api/{ns}/{table}`               | write `ns` | Delete a table                  |
+| `GET`    | `/api/{ns}/{table}/rows`          | read `ns`  | List rows (filter with `?col=value`) |
+| `POST`   | `/api/{ns}/{table}/rows`          | write `ns` | Create a row (body = its fields)|
+| `GET`    | `/api/{ns}/{table}/rows/{id}`     | read `ns`  | Get one row                     |
+| `PUT`    | `/api/{ns}/{table}/rows/{id}`     | write `ns` | Replace a row's fields          |
+| `DELETE` | `/api/{ns}/{table}/rows/{id}`     | write `ns` | Delete a row                    |
+
+In the web UI, open a table and use the **Columns** designer to add/remove
+columns; they persist and appear in the grid and the add-row form even with no
+rows yet.
 
 ```bash
-# create — POST to the namespace, key in the body
-curl -X POST localhost:8000/api/demo \
-  -H 'Content-Type: application/json' \
-  -d '{"key":"greeting","value":"hello","type":"string"}'
+curl -X POST localhost:8000/api/namespaces -H 'Content-Type: application/json' -d '{"name":"demo"}'
+curl -X POST localhost:8000/api/demo       -H 'Content-Type: application/json' -d '{"name":"users"}'
 
-# update — PUT to the entry's URI
-curl -X PUT localhost:8000/api/demo/greeting \
+# a row IS its fields — any shape you like
+curl -X POST localhost:8000/api/demo/users/rows \
   -H 'Content-Type: application/json' \
-  -d '{"value":"hi there","type":"string"}'
+  -d '{"name":"alice","age":30,"active":true}'
+# -> {"id":"<row-id>","updated_at":"...","fields":{...}}
 
-curl localhost:8000/api/demo          # list entries
+curl localhost:8000/api/demo/users/rows
+# -> {"columns":["name","age","active", ...], "rows":[{"id":..., "fields":{...}}, ...]}
+
+# filter by column conditions — each query param is a column=value test,
+# and multiple are AND-ed together:
+curl "localhost:8000/api/demo/users/rows?status=ok&ean=123"
 ```
 
-(The names `namespaces`, `health`, and `whoami` are reserved and can't be used
-as namespaces, since they'd collide with the routes above.)
+Filter values are matched leniently: `ean=123` matches a numeric `123` or the
+string `"123"`, `active=true` matches the boolean. The web UI has a matching
+**filter** box on each table (type `status=ok&ean=123`).
+
+(The names `namespaces`, `health`, `whoami`, `keys`, `accounts`, `login`,
+`logout`, `password`, and `me` are reserved and can't be used as namespaces.)
 
-The API is self-documenting via OpenAPI. Interactive docs are available at:
+The API is self-documenting via OpenAPI:
 
 - **`/docs`** — Swagger UI (also linked as **API docs** in the web interface header)
 - **`/redoc`** — ReDoc
@@ -129,24 +151,20 @@ The API is self-documenting via OpenAPI. Interactive docs are available at:
 When auth is enabled, each operation in Swagger exposes an `X-API-Key` header
 field you can fill in to try requests.
 
-### CSV import / export (web UI only)
+### CSV import / export (web UI only, per table)
 
-The web interface has **Download CSV** / **Import CSV** buttons on each
-namespace. These are a convenience of the web UI only — they are built on the
-regular entry API (export reads the entries; import creates/updates each row),
-so there are no dedicated CSV endpoints. The CSV has three columns —
-`key`, `type`, `value`:
+Each table in the web UI has **Download CSV** / **Import CSV** buttons. A table
+maps naturally to CSV: the header row is the column names, each line is a row.
+These are built on the rows API (no dedicated CSV endpoints). On import, each
+cell is parsed leniently — `30` → number, `true` → boolean, `[1,2]` → array,
+anything else → string.
 
 ```csv
-key,type,value
-name,string,alice
-count,number,7
-tags,array,"[""x"", ""y""]"
+name,age,active
+alice,30,true
+bob,25,false
 ```
 
-On import the `type` column is optional — if omitted, each value's type is
-inferred from its text.
-
 ### Access control (accounts + API keys)
 
 Off by default. **Turn it on** with `auth: true` in `tds.yml`, `--auth`, or
@@ -182,9 +200,9 @@ Each signed-in user can mint a personal **API key** (web UI → *My API keys*, o
 
 ```bash
 # the token is returned once; then use it as a header
-curl -X POST localhost:8000/api/projects \
+curl -X POST localhost:8000/api/projects/people/rows \
   -H "X-API-Key: $TOKEN" -H "Content-Type: application/json" \
-  -d '{"key":"env","value":"staging","type":"string"}'
+  -d '{"name":"alice","role":"qa"}'
 ```
 
 #### Auth & admin endpoints (summary)
@@ -211,7 +229,9 @@ environment variables:
 
 | YAML key   | Env var            | Default      | Purpose                                  |
 |------------|--------------------|--------------|------------------------------------------|
-| `data_dir` | `TDS_DATA_DIR`     | `./tds-data` | Namespace files + `.auth/` live here     |
+| `data_dir` | `TDS_DATA_DIR`     | `./tds-data` | Data + `.auth/` live here                |
+| `storage`  | `TDS_STORAGE`      | `sqlite`     | Storage backend: `sqlite` or `file`      |
+| `db_path`  | `TDS_DB_PATH`      | `<data_dir>/tds.db` | SQLite DB path (sqlite backend)   |
 | `auth`     | `TDS_AUTH_ENABLED` | `false`      | Turn access control on/off               |
 | `host`     | —                  | `127.0.0.1`  | Bind host                                |
 | `port`     | —                  | `8000`       | Bind port                                |
@@ -220,8 +240,17 @@ environment variables:
 | `api_keys` | `TDS_API_KEYS`     | *(empty)*    | Seed machine keys + grants               |
 | —          | `TDS_KEY_PEPPER`   | *(empty)*    | Optional pepper for API-key hashing      |
 
-Credentials live under `<data_dir>/.auth/` (`accounts.json`, `keys.json`,
-`secret`) — all hashed/secret material, never plaintext passwords or tokens.
+#### Storage backend
+
+Data is kept in **SQLite** by default — a single `tds.db` file the app creates
+in `data_dir` on first start (no setup, no server). Rows store their dynamic
+fields in a JSON column, so the schema is fixed while the data stays free-form.
+Set `storage: file` to use one JSON file per namespace instead (human-readable
+and dependency-free, but it rewrites a whole file per change and isn't safe
+across processes). Either way, point `data_dir` at a persistent volume.
+
+Credentials always live under `<data_dir>/.auth/` (`accounts.json`,
+`keys.json`, `secret`) — hashed/secret material, never plaintext.
 
 ### Tests
 

{test_data_service-0.2.0 → test_data_service-0.3.0}/src/test_data_service.egg-info/SOURCES.txt

@@ -22,6 +22,7 @@ src/testdataservice/config.py
 src/testdataservice/keystore.py
 src/testdataservice/passwords.py
 src/testdataservice/sessions.py
+src/testdataservice/sqlite_storage.py
 src/testdataservice/storage.py
 src/testdataservice/types.py
 src/testdataservice/web/static/app.js

test_data_service-0.3.0/src/testdataservice/__init__.py

@@ -0,0 +1,36 @@
+"""Test Data Service — a disk-backed namespace/table/row store with an API and web UI."""
+
+from .app import create_app
+from .config import Config
+from .storage import (
+    Storage,
+    FileStorage,
+    StorageBackend,
+    open_storage,
+    Row,
+    NamespaceNotFoundError,
+    TableNotFoundError,
+    TableExistsError,
+    RowNotFoundError,
+    InvalidNamespaceError,
+    InvalidTableError,
+)
+from .sqlite_storage import SqliteStorage
+
+__version__ = "0.1.0"
+__all__ = [
+    "create_app",
+    "Config",
+    "Storage",
+    "FileStorage",
+    "SqliteStorage",
+    "StorageBackend",
+    "open_storage",
+    "Row",
+    "NamespaceNotFoundError",
+    "TableNotFoundError",
+    "TableExistsError",
+    "RowNotFoundError",
+    "InvalidNamespaceError",
+    "InvalidTableError",
+]