jonkeane.com valid

dittodb

dittodb is a package that makes testing against databases easy. When writing code that relies on interactions with databases, testing has been difficult without recreating test databases in your continuous integration (aka CI) environment, or resorting to using SQLite databases

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-24T18:40:21.105Z. Cached copy · Source on jonkeane.com

# dittodb

`dittodb` is a package that makes testing against databases easy. When
writing code that relies on interactions with databases, testing has
been difficult without recreating test databases in your continuous
integration (aka CI) environment, or resorting to using SQLite databases
instead of the database engines you have in production. Both have their
downsides: recreating database infrastructure is slow, error prone, and
hard to iterate with. Using SQLite works well, right up until you use a
feature (like [a full outer join](https://www.sqlite.org/omitted.html))
or has [quirks](https://www.sqlite.org/quirks.html) that might differ
from your production database. `dittodb` solves this by recording
database interactions, saving them as mocks, and then replaying them
seamlessly during testing. This means that if you can get a query from
your database, you can record the response and reliably reproduce that
response in tests.

`dittodb` is heavily inspired by
[{httptest}](https://CRAN.R-project.org/package=httptest), if you’ve
used {httptest} before, you’ll find many of the interactions similar.

## A quick example

Say we have a database with some
[{nycflights}](https://CRAN.R-project.org/package=nycflights13) data in
it and we are writing functions that query this data that we want to
test.

For example, we have the simple function that retrieves one airline:

``` r
get_an_airline <- function(con) {
  return(dbGetQuery(con, "SELECT carrier, name FROM airlines LIMIT 1"))
}
```

But we want to make sure that this function returns what we expect. To
do this, we first record the response we get from the production
database:

## 

- RMariaDB
- RPostgres
- RSQLite

``` r
start_db_capturing()

con <- DBI::dbConnect(
  RMariaDB::MariaDB(),
  dbname = "nycflights"
)

get_an_airline(con)
DBI::dbDisconnect(con)

stop_db_capturing()
```
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=jonkeane.com · GET /v1/domain/jonkeane.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for jonkeane.com:
1. POST https://agentwebmap.com/v1/sites/jonkeane.com/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://jonkeane.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/jonkeane.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/jonkeane.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.